A product can contain an unlimited number of purchase details.
A purchase detail always consists of a unit definition. An example of this is a unit of 5 pieces. For more complex purchasing information, an additional content unit definition can be used. An example would be 2 boxes containing 5 pieces each.
In the information, the terms purchase unit and purchase content unit are used. The purchase unit is the combination of the order factor and the associated packaging or dimension. The minimum order quantity is not part of the purchase unit. The purchase content unit is used only in situations where additional detailed information is required about the contents of a purchase unit, such as the number of pieces in a box.
Sub-tab General
The purchasing information is divided into a logistics section and a pricing section.
| Supplier | Supplier linked to the purchase detail. |
| External code | Code of the product in the supplier’s product file. This field is almost never used and is intended for very specific product integrations. The recommendation is to leave this field empty under normal circumstances. |
| Order code | The code under which this purchase line is known at the supplier. For EDI orders this field is not used, as EDI messages always work exclusively with barcodes. |
| Purchase unit barcode | The barcode under which this purchase line is known at the supplier. For EDI orders it depends on the supplier settings whether the sales barcode or the purchase barcode is used. |
| Minimum order quantity | Minimum order quantity |
| Order factor | The number of pieces contained in one purchase unit. |
| Purchase unit packaging/dimension | The packaging or dimension of the purchase unit. Examples of packaging are box or pieces; examples of dimensions are kilogram, cubic meter, etc. |
| Cubic meters per unit | How many cubic meters one purchase unit represents. This information can be used in webshop order handling to determine total delivery volume. |
| Standard delivery days | The number of days it normally takes to receive this purchase unit. This value is taken into account when automatically calculating minimum and maximum stock levels; the longer the delivery time, the more stock must be kept in reserve. |
| Content unit packaging/dimension | When purchase units require a sub-unit, the content of a purchase unit can be defined here. |
| One purchase unit contains x content units | The number of content units included in one purchase unit. |
| One content unit equals x SKU | How one content unit is converted into stock (stock keeping unit). |
| Preferred line | Per product and supplier, one purchase line can be marked as the preferred line. This line will be ordered by default when this supplier is selected. With system settings it is possible to calculate the most suitable purchase line instead. |
| Purchase status | The status of the purchase line indicates whether it is expired and whether it can be ordered. Purchase status values are fully configurable. |
| Purchase price group | It is possible to record alternative purchasing information, for example purchasing data per container. Purchase data assigned to a purchase price group is ignored in the normal purchasing process. |
RetailVista supports various purchase prices in the purchase details. It is not required to use all price fields. RetailVista first uses the custom purchase price (if entered), then the net purchase price, and finally the gross purchase price.
| Purchase prices per | Purchase prices can be defined for different parts of the logistic data.
| ||||||
| Gross purchase price | The standard catalogue purchase price, without discounts or surcharges. | ||||||
| Discount percentage | When a discount percentage is entered, RetailVista will automatically calculate the purchase price. | ||||||
| Net purchase price | The net purchase price is the price that will actually be paid when ordering the product, and is also used when calculating the stock value. | ||||||
| Per quantity | The gross, net, and custom purchase prices apply to the quantity defined here. The default is 1, meaning the price applies to 1 stock keeping unit or 1 purchase unit or 1 purchase content unit, depending on the chosen level. | ||||||
| Custom purchase price | The custom purchase price always overrides the gross and net purchase prices if entered. In general, gross and net prices are supplied by the supplier; this field allows a different custom price to be recorded. | ||||||
| Comment | Free text. | ||||||
| Net/net | This option indicates that no further discounts may be applied to the resulting purchase price, such as order discounts or performance discounts. If a purchase price is marked as net/net, it becomes the final price applied in the purchase order and is used to calculate the total purchase order value. | ||||||
Examples of purchase details:
1 x 10 pieces (the purchase unit is 10 pieces)
| Minimum order quantity | 1 |
| Order factor | 10 |
| Packaging | Pieces |
5 x 10 pieces (the purchase unit is 10 pieces)
| Minimum order quantity | 5 |
| Order factor | 10 |
| Packaging | Pieces |
10 x 1 box of 24 pieces (the purchase unit is 1 box, the content unit is 24 pieces). In this example, the SKU is defined as 1 piece. A box of 24 pieces is therefore converted into 24 stock units. With an order of 10 x 1 box, the SKU/stock will be 240.
| Minimum order quantity | 10 |
| Order factor | 1 |
| Packaging | Box |
| Minimum order quantity | 10 |
| Order factor | 1 |
| Packaging | Box |
| Content unit | Pieces |
| Purchase unit contains x content units | 24 |
| One purchase unit equals x SKU | 24 |
1 x 10 rolls of 100 meters (the purchase unit is 10 rolls). The SKU in this example is defined as 1 meter. A roll of 100 meters is therefore converted into 100 stock units. With an order of 10 rolls, the SKU/stock will be 1000.
| Minimum order quantity | 1 |
| Order factor | 10 |
| Packaging | Roll |
| Content unit | Meter |
| Purchase unit contains x content units | 100 |
| One purchase unit equals x SKU | 100 |