Pricing Rules

All of STORIS's point of sale processes adhere to the following pricing hierarchy when determining a default selling price for order items. The hierarchy starts with rule 1, checking each rule until it finds a price.

Next, if a customer price matrix exists (see Customer Price Matrices below) for the customer/product combination, the system compares that price to the hierarchy price. Depending on which is higher or lower, various results can occur as described below.  If the system cannot find a price within the hierarchy and no customer price matrix exists, no price defaults on the order.

Pricing Hierarchy

For each sales order item, the pricing hierarchy checks the

  1. Enter a Stock Adjustment routine to determine if any of the products have special as-is pricing applied.  You establish as-is pricing via the As-Is Selling Price field on the Move to As-Is tab. Note that Twilight Discount Pricing is a type of as-is pricing, and the system checks for Twilight pricing before it checks for other as-is pricing.

  2. Pricing Level Table in the Advanced Product Settings. If Level Pricing is active on your system, the Level Pricing table overrides all other pricing considerations except as-is pricing.  

  3. Price/Spiff/Commission Table. For all products for which you set up a price/spiff/commission table, STORIS' pricing hierarchy references this table on two levels:

  1. For each price range you set up in this table, you can specify a price category. In order entry, if one of these price categories matches the customer's price category from the Customer Settings, order-entry applies the price associated with the price category.  

  2. If no price categories in the table match the customer's price category, order-entry uses the highest price specified in the table, provided a lower promotional price has not been specified elsewhere (see below), in which case it uses the first promotional price it finds that is lower.

  1. District and Regional Product Settings. This file contains price exceptions by district and region. The system checks this file for promotional sale price exceptions for the district in which each order originates.  This is the first level checked in the “standard” pricing hierarchy.

  2. *Advanced Product Settings (Pricing tab) to determine if a general promotional sale is in progress for the selected product.

  3. *Warehouse Inventory Settings to determine if a price by location exists for the selected product.

  4. District and Regional Product Settings. This file contains price exceptions by district and region. The system checks this file again (see step 4) to determine if a regular selling price, specific to the district in which the order originates, exists for the selected product.

  5. Advanced Product Settings (Selling Price field).

*If you enable the Use Warehouse Inventory field on the Miscellaneous tab of the Warehouse/Store Location Settings, the pricing hierarchy uses the warehouse inventory price ahead of the promotional price. That is, the warehouse inventory price moves to number 5 in the pricing hierarchy and the promotional price drops to number 6.

When a kit's pricing is set to Component (Source of Price field in Product Kit Settings), it overrides the Location Selling Price $ in Warehouse Inventory Settings. The Warehouse Inventory Settings price is used only if the Source of Price for the kit master is set to Product.

Customer Price Matrices

The Customer Price Settings allow you to create customer price matrices for selected customer/product combinations.  If a customer price matrix exists for a piece on an order and the matrix price is lower than the price returned by the pricing hierarchy, order entry applies the matrix price, provided the pricing hierarchy does not apply a price from the Pricing Level table or the Price/Spiff/Commission Table, both of which override the price (if any) from the Customer Price Settings.

Markdown Prices

In order entry, if the program finds a markdown price for an order item, the program uses the markdown price unless the default selling price is lower, in which case it uses the default price.  To establish markdown prices for selected products, use any of the following routines: