Module Products - Revision history

Techsc: /* Related videos */ Not in the language of the page but it's better than nothing or it can help

2022-10-24T17:22:49Z

Related videos: Not in the language of the page but it's better than nothing or it can help

← Older revision		Revision as of 17:22, 24 October 2022
Line 96:		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>

Eldy: /* Rules to manage sales prices */

2022-04-30T12:39:40Z

Rules to manage sales prices

← Older revision		Revision as of 12:39, 30 April 2022
Line 64:		Line 64:

	*One and only one price per product		*One and only one price per product
	*Different prices per segment of customers (~~each customer is inside one "level", and each level can have a different prices~~)		*Different prices per segment of customers (see next chapter)
	*Different prices per customer		*Different prices per customer
	*Different prices per quantity (experimental)		*Different prices per quantity (experimental)

Eldy: /* Rules to manage sales prices */

2022-04-30T12:38:35Z

Rules to manage sales prices

← Older revision		Revision as of 12:38, 30 April 2022
Line 64:		Line 64:

	*One and only one price per product		*One and only one price per product
	*~~different~~ prices per segment of customers		*Different prices per segment of customers (each customer is inside one "level", and each level can have a different prices)
	*~~different~~ prices per customer		*Different prices per customer
	*~~different~~ prices per quantity (experimental)		*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===

Eldy: /* Virtual products (kits, also called Pack products) */

2022-04-30T12:36:43Z

Virtual products (kits, also called Pack products)

← Older revision		Revision as of 12:36, 30 April 2022
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)

	==~~Virtual~~ products (~~kits,~~ also called Pack ~~products~~)==		==Kits products (also called Pack Products or Virtual Products)==
	A product or service may be registered as a ~~virtual~~ (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 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 ~~virtual~~ product complies with the following rules:		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 which will then be kept in stock as such.		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 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.		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.		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.

Christof: /* Rules to manage sales prices */ sales prices instead of sale price - to avoid confusion

2020-09-22T22:16:42Z

Rules to manage sales prices: sales prices instead of sale price - to avoid confusion

← Older revision		Revision as of 22:16, 22 September 2020
Line 60:		Line 60:

	==Rules to manage sales prices==		==Rules to manage sales prices==
	There are 4 ways to manage ~~sale price of products~~ in Dolibarr.		There are 4 ways to manage sales prices in Dolibarr.

	*One and only one price per product		*One and only one price per product
	*~~Price~~ per segment of customers		*different prices per segment of customers
	*~~Price~~ per customer		*different prices per customer
	*~~price~~ per quantity (experimental)		*different prices per quantity (experimental)

	===Price per segment of customers===		===Price per segment of customers===

Christof: /* Virtual products (kits, also called Pack products) */ only grammar.

2020-09-22T22:11:59Z

Virtual products (kits, also called Pack products): only grammar.

← Older revision		Revision as of 22:11, 22 September 2020
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 to be kept in stock.		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 ~~are~~ only decrementing the stock at the time of delivery of the virtual product. Till then, these sub-products remain at disposal to be integrated in ~~the~~ sales ~~process~~ as single independent products also. Again, the ''manufacturing'' module ~~on the contrary,~~ from the moment it registered a "container product", immediately purveyed that its by-products were unusable for any other purpose. Therefore, their stock was 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.		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 ~~change~~ this ~~number~~.		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==

Christof: Some editing for comprehension to match the French description of the virtual product module description.

2020-09-22T22:06:10Z

Some editing for comprehension to match the French description of the virtual product module description.

← Older revision		Revision as of 22:06, 22 September 2020
Line 17:		Line 17:
	userdoc=This page\|}}		userdoc=This page\|}}

	= Introduction =		=Introduction=
	This module manages the product catalog.		This module manages the product catalog.

	See also [[Module Services En\|Modules Services]] to manage a catalog of services, or page [[Module Stocks En\|Module Stocks]] to manage warehouses and stock.		See also [[Module Services En\|Modules Services]] to manage a catalog of services, or page [[Module Stocks En\|Module Stocks]] to manage warehouses and stock.

	= Installation =		=Installation=
	{{NoInstallModuleEn}}		{{NoInstallModuleEn}}

	= Configuration =		=Configuration=
	{{ActivationModuleEn}}		{{ActivationModuleEn}}

	= Definition =		=Definition=
	== Products ==		==Products==
	A ''product'' is an object you sell to customers or it is an object you buy from suppliers. It is a physical object as opposed to [[ServicesEn\|Services]].		A ''product'' is an object you sell to customers or it is an object you buy from suppliers. It is a physical object as opposed to [[ServicesEn\|Services]].

	A product follows this rules:		A product follows this rules:
	* A product can be stocked into a warehouse (only products appears in module [[Module_StockEn\|Stock]]. Services are not visible).
	* A product can be delivered (only products appears in module [[Module Shipment\|Shipment]]. Services are not visible. Services are realized but cannot be shipped).		*A product can be stocked into a warehouse (only products appears in module [[Module_StockEn\|Stock]]. Services are not visible).
	* A product is a material good. It's value often decreases with time (the value of a used product is less than a new product).		*A product can be delivered (only products appears in module [[Module Shipment\|Shipment]]. Services are not visible. Services are realized but cannot be shipped).
			*A product is a material good. It's value often decreases with time (the value of a used product is less than a new product).

	Some fields are dedicated to products and not available for Services like:		Some fields are dedicated to products and not available for Services like:
	* Weight
	* Size
	* Customs code = Commodity code = License code = HTS (An international 6 character code to define the category of product)

	== Virtual products (kits, also called Pack products) ==		*Weight
	A product or service may be a virtual (parent) product ~~comprising~~ other (~~real~~) products. This function is activated from the Products ~~module~~ or the Service ~~configuration~~ page. It allows "packages" or "kits" of products ~~that for use in~~ orders, invoices and inventory ~~as a single element~~ instead of the ~~n products as Lot~~.		*Size
			*Customs code = Commodity code = License code = HTS (An international 6 character code to define the category of product)

			==Virtual products (kits, also called Pack products)==
			A product or service may be registered as a virtual (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 virtual product complies with the following rules:		A virtual product complies with the following rules:
	* When adding a product in a document (proposals, invoice, order), only the line of the virtual parent ~~product~~ is shown.
	* The stock of ~~the~~ individual ~~components of~~ the virtual product is incremented / decremented when the ~~virtual~~ product is ~~incremented~~ / ~~decremented~~.		*When adding a product in a document (proposals, invoice, order), only the line of the virtual product (the "parent") is shown.
	* A virtual product may itself be composed of other virtual products that contain ~~the physical~~ products.		*The stock of each individual component inside the virtual product is incremented / decremented when the parent product is acquired / delivered.
			*A virtual product may itself be composed of other virtual products that contain other (single) products.

	Note:		Note:
	It is ~~not~~ a function of "manufacturing / production" where the ~~virtual product component products are consumed son~~ of ~~stock father for~~ an additional product in stock.		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 to be kept in stock.
	Here, the sub-components ~~produced~~ a virtual product are ~~decremented~~ stock at the time of ~~consumption~~ of the virtual product ~~and~~ remain independent ~~manner consumables byproducts other~~, ~~unlike a~~ manufacturing module, ~~wherein when~~ that a by-~~product is used to manufacture a father module~~, ~~the products under the same~~ stock is decremented if the ~~father~~ product ~~is not yet distributed~~, ~~and often this byproducts can~~ no longer ~~do the~~ reverse ~~way back~~ in stock.		Here in fact, in the "virtual product or service" function, the sub-components of a virtual product are only decrementing the stock at the time of delivery of the virtual product. Till then, these sub-products remain at disposal to be integrated in the sales process as single independent products also. Again, the ''manufacturing'' module on the contrary, from the moment it registered a "container product", immediately purveyed that its by-products were unusable for any other purpose. Therefore, their stock was 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 ~~sale~~ prices ==		==Rules to manage sales prices==
	There are 4 ways to manage sale price of products in Dolibarr.		There are 4 ways to manage sale price of products in Dolibarr.

	*One and only one price per product		*One and only one price per product
	*Price per segment of customers		*Price per segment of customers
Line 62:		Line 66:

	===Price per segment of customers===		===Price per segment of customers===
	Dolibarr can accept several prices per customer segment. By default, there is 5 segments (so 5 groups of different customers), but you can change this number.		Dolibarr can accept several prices per customer segment. By default, there are 5 segments (i.e. 5 groups of different customers), but you can change this number.
	Each customer can be ~~into~~ 1 and only 1 segment and will ~~use~~ the price defined for ~~its~~ segment (or segment 1 if the segment ~~of customer~~ is not 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 ~~support~~ getting but not setting multiprices per segment for a product. ~~Price~~ for a product and customer segment can be set from 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==
	Products can be added to one or multiple categories.		Products can be added to one or to multiple categories.

	To set categories of a product with API, you must use the APIs /categories/...		To set categories of a product with API, you must use the APIs /categories/...

	== Image ==		==Image==
	A product can have one or multiple images. This can be manually set from the tab "Linked files" of a product.		A product can have one or multiple images. This can be manually set from the tab "Linked files" of a product.

	To get or set an image of a product using the APIs, you must use the API /documents (with "modulepart" parameter = "product" or "service").		To get or set an image of a product using the APIs, you must use the API /documents (with "modulepart" parameter = "product" or "service").

	== Variants ==		==Variants==
	A product can have multiple variants, e.g. for sizes or colors.		A product can have multiple variants, e.g. for sizes or colors.

	As of v12 the REST API supports both getting, setting and deleting variants for a product.		As of v12 the REST API supports both getting, setting and deleting variants for a product.

	= Life cycle / Business rules =		=Life cycle / Business rules=
	{{ToComplete}}		{{ToComplete}}

	= Related videos =		=Related videos=
	<youtube width="200" height="120">Qm0k1G4BYsE</youtube>		<youtube width="200" height="120">Qm0k1G4BYsE</youtube>

Eldy at 15:10, 23 August 2020

2020-08-23T15:10:46Z

← Older revision		Revision as of 15:10, 23 August 2020
Line 85:		Line 85:
	{{ToComplete}}		{{ToComplete}}

	= ~~Examples of use cases~~ =		= Related videos =
	~~{{ToComplete}}~~		<youtube width="200" height="120">Qm0k1G4BYsE</youtube>
	~~{{ExamplesCaseEn~~
	~~\|name=UCMP01:~~
	~~\|situation~~=
	~~\|actions~~=
	~~}} ~~

Eldy: /* Price per segment */

2020-07-20T00:56:08Z

Price per segment

← Older revision		Revision as of 00:56, 20 July 2020
Line 61:		Line 61:
	*price per quantity (experimental)		*price per quantity (experimental)

	===Price per segment===		===Price per segment of customers===
	Dolibarr can accept several prices per customer segment. By default, there is 5 segments (so 5 groups of different customers), but you can change this number.		Dolibarr can accept several prices per customer segment. By default, there is 5 segments (so 5 groups of different customers), but you can change this number.
	Each customer can be into 1 and only 1 segment and will use the price defined for its segment (or segment 1 if the segment of customer is not defined).		Each customer can be into 1 and only 1 segment and will use the price defined for its segment (or segment 1 if the segment of customer is not defined).

Eldy: /* Multiprices */

2020-07-20T00:55:47Z

Multiprices

← Older revision		Revision as of 00:55, 20 July 2020
Line 54:		Line 54:
	Here, the sub-components produced a virtual product are decremented stock at the time of consumption of the virtual product and remain independent manner consumables byproducts other, unlike a manufacturing module, wherein when that a by-product is used to manufacture a father module, the products under the same stock is decremented if the father product is not yet distributed, and often this byproducts can no longer do the reverse way back in stock.		Here, the sub-components produced a virtual product are decremented stock at the time of consumption of the virtual product and remain independent manner consumables byproducts other, unlike a manufacturing module, wherein when that a by-product is used to manufacture a father module, the products under the same stock is decremented if the father product is not yet distributed, and often this byproducts can no longer do the reverse way back in stock.

	== ~~Multiprices~~ ==		== Rules to manage sale prices ==
	There are ~~3 types~~ of ~~multiprices~~ in Dolibarr.		There are 4 ways to manage sale price of products in Dolibarr.
	*price per ~~customer~~		*One and only one price per product
	*~~price~~ per segment of customers		*Price per segment of customers
	*price per ~~customer~~		*Price per customer
			*price per quantity (experimental)

	===Price per segment===		===Price per segment===