148
edits
Module Products: Difference between revisions
→Related videos: Not in the language of the page but it's better than nothing or it can help
m (Some editing for comprehension to match the French description of the virtual product module description.) |
(→Related videos: Not in the language of the page but it's better than nothing or it can help) Tag: 2017 source edit |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 44: | Line 44: | ||
*Customs code = Commodity code = License code = HTS (An international 6 character code to define the category of product) | *Customs code = Commodity code = License code = HTS (An international 6 character code to define the category of product) | ||
== | ==Kits products (also called Pack Products or Virtual Products)== | ||
A product or service may be registered as a | A product or service may be registered as a Kit (a "parent") product, that is, containing other (single) products. This function is activated from the ''Products'' or the ''Service'' module settings page. It allows "packages" or "kits" of products to be dealt with as a single lot, within orders, invoices and inventory, instead of dealing individually with the components. | ||
A | A Kit product complies with the following rules: | ||
*When adding a product in a document (proposals, invoice, order), only the line of the virtual product (the "parent") is shown. | *When adding a product in a document (proposals, invoice, order), only the line of the virtual product (the "parent") is shown. | ||
| Line 54: | Line 54: | ||
Note: | Note: | ||
This is meant as a distinct function from "manufacturing / production" where another "container" product uses the existing stock of its sub-components to produce an additional product | |||
Here in fact, in the " | This is meant as a distinct function from "manufacturing / production" where another "container" product uses the existing stock of its sub-components to produce an additional product which will then be kept in stock as such. | ||
Here in fact, in the "kit product or service" function, the sub-components of a virtual product will only be decrementing the respective stock at the time of delivery of the virtual product. Till then, these sub-products remain at full disposal, to be possibly integrated in other sales processes as single independent products also. | |||
Again, the ''manufacturing'' module acted differently : from the moment it registered a "container product", it immediately purveyed that its by-products were unusable for any other purpose. Therefore, their stock was immediately decremented whether or not the container product left the store, as it was to be considered that the sub-components could no longer be reverse engineered as single products in stock. | |||
==Rules to manage sales prices== | ==Rules to manage sales prices== | ||
There are 4 ways to manage | There are 4 ways to manage sales prices in Dolibarr. | ||
*One and only one price per product | *One and only one price per product | ||
* | *Different prices per segment of customers (see next chapter) | ||
* | *Different prices per customer | ||
* | *Different prices per quantity (experimental) | ||
You must choose one and only one into the Setup of the module "Products". | |||
===Price per segment of customers=== | ===Price per segment of customers=== | ||
Dolibarr can accept several prices per customer segment. By default, there are 5 segments (i.e. 5 groups of different customers), but you can | Dolibarr can accept several prices per customer segment. By default, there are 5 segments (i.e. 5 groups of different customers), but you can also edit this figure. | ||
Each customer can be associated with 1 and only 1 segment, and therefore he or she will be assigned the price defined for that segment (segment 1 if the customer segment is not yet defined). | Each customer can be associated with 1 and only 1 segment, and therefore he or she will be assigned the price defined for that segment (segment 1 if the customer segment is not yet defined). | ||
As of v12 the REST API supports getting but not setting multiprices per segment for a product. Prices for a product and customer segment can be set from the backoffice only. | As of v12 the REST API supports getting, but not setting, multiprices per segment for a product. Prices for a product and customer segment can be set from the backoffice only. | ||
==Categories== | ==Categories== | ||
| Line 91: | Line 96: | ||
=Related videos= | =Related videos= | ||
<youtube width="200" height="120">Qm0k1G4BYsE</youtube> | <youtube width="200" height="120">Qm0k1G4BYsE</youtube> | ||
(vocal in french but subtitles are available and review in this language) | |||
<youtube width="200" height="120">pm5i_1ij2zw</youtube> | |||