Another essential part of the Price entity is identification of the product that will be configured. In Price it is necessary to set the vendorItemId which is the unique identifier of the product from a vendor perspective, as well as the sku. Although in most cases the sku can be equal to the vendorItemId, in some cases it can differ and must be set accordingly to what was registered in Items MS.

The pricing of the product can be set in two distinct types, and the key definition, as well as examples of each one are describe below:

Price Type:

• Price Per Unit [PER_UNIT]:

  • The price per unit is the most used price type, and it defines a cost for a single unit of a product;

  • Lets assume that there is a beer and it must be sold for 10$ each bottle. Given that the product is sold per bottle, each unit will cost precisely 10$.

• Price Per Unit Of Measurement [PER_UOM]

  • The price per unit of measurement is not often used, because is related to specific products that the price fluctuates based on the amount of quantity added by the customer;

  • For example, let's assume a partner wants to sell ham in BEES, however, they do not have a specific packaging with a final quantity. They do want to sell it and they have established that each 1 kilogram is worth 15$. For this scenario, the Price Per Unit Of Measurement must be used.

Base Price:

• A substantial element of the Price is the basePrice, the base price represents the price for a specific product. It can be the price without any taxes or it can include taxes and other fees:

  • One important thing to notice that if the basePrice already includes taxes, the customer won't have the visibility that taxes are being applied to that product;

  • Discounts are applicable taken into consideration the basePrice, therefore if taxes are included it may lead to a discount in the tax value as well.

Measure Unit:

• Measure unit is a mandatory property of price and was mainly used to when products are priced per unit of measurement. However, due to being mandatory it needs to be populated even if the price type is set as PER_UNIT.

Minimum Price:

• Minimum Price is a property that establishes the minimum price that this product can be sold at even if discounts are applied;

• Let's assume a product is priced as 10$. The minimum price is set as 5$. Then a discount created for this product with 80% discount. Instead of being able to view the product with discount priced at 2$ (80% of 10$), the customer will view the price as 5$. This scenario occurs because even though there is a 80% discount applied to the product, the result falls below the threshold of 5$ (minimum price), then BEES will set the price as the minimum price, obeying the limit.