15
edits
Module Products: Difference between revisions
m
→Virtual products (kits, also called Pack products): only grammar.
m (Some editing for comprehension to match the French description of the virtual product module description.) |
m (→Virtual products (kits, also called Pack products): only grammar.) |
||
| 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 | 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 "virtual product or service" function, the sub-components of a virtual product | Here in fact, in the "virtual 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== | ||
| Line 66: | Line 68: | ||
===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== | ||