Product maintenance
- 02 Jun 2024
- 6 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Product maintenance
- Updated on 02 Jun 2024
- 6 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Product maintenance is an important basic module of RetailVista. By creating a product, it is available in various modules for ordering, purchasing, etc. Due to the extensive number of fields, the product card is divided into different tabs. The following tabs and fields are available:
General Tab
-
Purchasing Tab
Using purchasing data, RetailVista knows which suppliers can deliver a product and based on which conditions. One or more purchasing data can be recorded per product. The same supplier can deliver the product in multiple packaging options, and it is also possible for different suppliers to deliver the same product. One purchasing data must be set as the preferred purchasing data per supplier. There is no limit to the number of purchasing data per product in RetailVista. In addition to these purchasing data, one preferred supplier must always be set. This is usually done automatically after creating the first purchasing data. Using the preferred supplier and the preferred purchasing rule, RetailVista knows from which supplier to order the product by default and in which packaging. However, there are settings that determine that RetailVista automatically determines the most suitable packaging, for example, rounding up or down to the nearest purchasing packaging.
Using the preferred supplier and the preferred purchasing rule, the net purchase price is known. With this net purchase price, RetailVista calculates the inventory value in various overviews. The exception to this is the possible use of FIFO (First in first out), which calculates the inventory value differently. For more information, see the help section of the inventory module.
A purchasing data always consists of a unit definition. An example of this is a unit of 5 pieces. For more complex purchasing information, an additional use of a content unit definition can be made.
An example of this is 2 boxes of 5 pieces each.
The information refers to the term "purchase unit" and "purchase content unit". The purchase unit is the combination of the order factor and the corresponding packaging or dimension. The minimum number to order is not part of the purchase unit. The purchase content unit is only used in situations where there are more detailed data about the content of a purchase unit. This could, for example, be the quantity of pieces in a box.
Subtab 'General'
The purchase information is divided into a logistics section and a price section.
| Supplier | Supplier in the purchase information |
| External code | Code of the item in the supplier's item file. This field is hardly ever used and is intended for very specific item integrations. The advice is to normally leave this field empty and not use it. |
| Order code | The code under which this purchase rule is known to the supplier. This field is not used for EDI orders, as EDI messages always and exclusively work with barcodes. |
| Purchase unit barcode | The barcode under which this purchase rule is known to the supplier. For EDI orders, it depends on the supplier's settings whether the sales barcode or the purchase barcode is used. |
| Minimum order quantity | The minimum number of purchase units to order. This refers to the combination of order factor and purchase unit. |
| Order factor | The number of pieces contained in 1 purchase unit. |
| Purchase unit packaging/dimension | The packaging or dimension of the purchase unit. An example of packaging is a box or pieces, an example of dimension is kilogram, m3, etc. |
| M3 per unit | How many m3 is 1 purchase unit. This information can be used in webshop order handling to determine the total delivery volume. |
| Standard delivery days | How many days does it take to deliver this purchase unit as standard. This case is taken into account when automatically calculating the min/max stock. The longer the delivery days, the more stock needs to be kept in reserve. |
| Content unit packaging/dimension | For purchase units where there is a need for a sub-unit, the content of a purchase unit can be specified here. |
| 1 Purchase unit contains x content units | How many content units are included in 1 purchase unit. |
| 1 Content unit is x SKU | How 1 content unit is converted to stock keeping unit (SKU) |
| Preference rule | For each product and supplier, 1 purchase rule can be marked as a preference rule. This rule will be ordered by default if this supplier is chosen. Settings can be used to indicate that the most suitable purchase rule should be calculated. |
| Purchase status | The purchase status indicates whether the purchase rule is expired or not, and whether it is orderable or not. The desired purchase status rules can be determined entirely by yourself. |
| Purchase price group | It is possible to record deviating purchase data, for example purchase data per container. Purchase data with a purchase price group are ignored in the normal purchase process. |
RetailVista has different purchase prices for purchase data. It is not mandatory to use all purchase price fields. RetailVista uses its own purchase price field first (if specified), then the net purchase price, and finally the gross purchase price.
| Purchase prices per | Purchase prices can be specified for different parts of the logistics data.
| ||||||
| Gross purchase price | The gross purchase price is the standard catalog purchase price, without discounts or surcharges. | ||||||
| Discount percentage | By specifying the discount percentage, RetailVista will automatically calculate the purchase price. | ||||||
| Net purchase price | The net purchase price is the price that will be paid when ordering the item and is also used to calculate the value of the inventory. | ||||||
| per quantity | The gross and net and own purchase price applies to the specified quantity. By default, this is 1, and for purchase prices per SKU, it means that the purchase prices apply to 1 inventory position. The same applies, of course, to purchase prices per purchase unit or purchase content unit. | ||||||
| Own purchase price | The own purchase price always takes precedence over the gross and net purchase price, if it is specified. In general, the gross and net purchase prices are provided by the supplier, but with this field, it is possible to record a different own price. | ||||||
| Note | Free text | ||||||
| Net/net | With the found purchase price, it can be indicated that no further discount may be applied. This includes order discounts, performance discounts, etc. If a purchase price is net/net, it will be the price applied in the purchase order and ultimately leads to a total purchase order value. |
Examples of purchase data:
1x 10 pieces (the purchase unit is therefore 10 pieces)
| Minimum order quantity | 1 |
| Order factor | 10 |
| Packaging | Pieces |
5 x 10 pieces (the purchasing unit is therefore 10 pieces)
| Minimum order quantity | 5 |
| Order factor | 10 |
| Packaging | Pieces |
10 x 1 box of 24 pieces (the purchasing unit is therefore 1 box, the content unit is 24 pieces). For the SKU (stock keeping unit), 1 piece has been chosen in this example. A box of 24 pieces is therefore converted to a stock position of 24 pieces. With the order of the example below of 10 x 1 box, the SKU / stock will be 240.
| Minimum order quantity | 10 |
| Order factor | 1 |
| Packaging | Box |
| Content unit | Pieces |
| Purchasing unit contains x content units | 24 |
| 1 Purchasing unit is x SKU | 24 |
1 x 10 roll of 100 meters (the purchasing unit is therefore 10 rolls). For the SKU (stock keeping unit), 1 meter has been chosen in this example. A roll of 100 meters must therefore be converted to a stock position of 100 pieces. With the order of the example below of 10 rolls, the SKU / stock will be 1000.
| Minimum order quantity | 1 |
| Order factor | 10 |
| Packaging | Roll |
| Content unit | Mtr |
| Purchase unit contains x content units | 100 |
| 1 Purchase unit is x SKU | 100 |
Was this article helpful?