odoo-addon-sale-order-type 19.0.1.6.0.1

Sale Order Type

Sale Order Type

This module adds a typology for the sales orders. In each different type, you can define, invoicing and refunding journal, a warehouse, a stock route, a sequence, the shipping policy, the invoicing policy, a payment term, a pricelist and an incoterm.

You can see sale types as lines of business.

You are able to select a sales order type by partner so that when you add a partner to a sales order it will get the related info to it.

When no partner or context default applies, the first available sale order type by sequence is used as the default.

Additionally, it adds a warning message to notify users when there is a mismatch between the partner’s default pricelist and the effective pricelist set by the sales order type. This ensures clarity when creating sales orders, as the effective pricelist (determined by the sales order type) will take precedence over the partner’s default pricelist. The warning is only visible for companies without a parent and when there is a mismatch between the two pricelists.

Table of contents

• Configuration

• Usage

• Bug Tracker

• Credits

  • Authors

  • Contributors

  • Maintainers

Configuration

To configure Sale Order Types you need to:

1. Go to Sales > Configuration > Sales Orders Types

2. Create a new sale order type with all the settings you want

3. Use the drag handle in the list view to define the priority of the sale order types. The first matching type for the current company is used as the default when no partner or context default applies.

Usage

1. Go to Sales > Sales Orders and create a new sale order. Select the new type you have created before and all settings will be propagated.

2. You can also define a type for a particular partner if you go to Sales & Purchases and set a sale order type.

3. When no type is set on the partner and no default is provided in the context, the sale order uses the first available type according to the sequence configured on sale order types.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• Grupo Vermon

• AvanzOSC

• Tecnativa

• Agile Business Group

• Niboo

Contributors

• Vermon

  • Carlos Sánchez Cifuentes <[e-mail]>

• AvanzOsc

  • Oihane Crucelaegui <[e-mail]>

  • Ana Juaristi <[e-mail]>

  • Daniel Campos <[e-mail]>

  • Ainara Galdona <[e-mail]>

• Agile Business Group

  • Lorenzo Battistini <[e-mail]>

• Niboo

  • Samuel Lefever <[e-mail]>

  • Pierre Faniel <[e-mail]>

• Tecnativa

  • Pedro M. Baeza

  • David Vidal

  • Carlos Dauden

  • Sergio Teruel

• Pesol

  • Angel Moya Pardo <[e-mail]>

  • Antonio J Rubio Lorente <[e-mail]>

• Rattapong Chokmasermkul <[e-mail]>

• Druidoo

  • Iván Todorovich <[e-mail]>

• GSLab.it

  • Giovanni Serra <[e-mail]>

• Tharathip Chaweewongphan <[e-mail]>

• Isaac Gallart <[e-mail]>

• Denis Rousse <[e-mail]>

• Camptocamp

  • Maksym Yankin

Do not contact contributors directly about support or help with technical issues.

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/sale-workflow project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.