Product & Price List Rules:

The Price List - Products (ibis_icplp.im18) view adheres to a number of rules:

  1. Products can be on multiple price lists.

  2. Selling prices can be zero but they cannot be negative. Gross Margin %, however, can be calculated and entered as a zero or a negative value until the resulting selling price reaches the zero mark.

  3. GM% is calculated using currency conversion, therefore foreign prices are converted to domestic for GM% calculations.

  4. Contract, special, flyer and common quote price lists are linked to a master price list (MPL). When assigning a product to one of these price lists, the product code must be on the MPL for the following 2 price methods:

    • Discount off Master
    • Master Price Multiplier

    For all other price methods (fixed price, gross margin, markup on cost) the product does not have to be on the MPL since these pricing methods do not use the MPL for the price calculation.

    If you want to only allow certain products to be purchased by a specific customer(s), create the product in the Products (ibis_ici1) view but do NOT add it to a MPL. Put the customer's price in a special or contract price list and link the customer to the special/contract in the customers (ibis_sucu)view; that customer will get a 'hit' in the pricing routing but no other customer will.

  5. The values assigned to the following pricing methods must be within the range identified:

    • Discount off Master - the discount must be between -100.00 and 100.00 or a valid chain discount with no more than 11 characters in total.
    • Master Price Multiplier - the multiplier (percent) must be between 0.0 and 99.9999.

  6. You can add common products as a group to a price list by entering the product prefix and color separator followed by an *. For example, the common products are 1234BEARS-RED, 1234BEARS-GREEN, 1234BEARS-BROWN, etc. To add the products as a group, simply enter 1234BEARS-* and all of the common products are added to the price list. For more information on common products, click here.

  7. When a product and commodity appear on the same price list and the product is part of the commodity code, the system takes the price for the product and does NOT consider the commodity price.

  8. In a paying office scenario, special pricing is per the price lists assigned in the paying office's Customer (ibis_sucu) record. If there are no contract/special price lists assigned to the paying office, then the customer's own contract/special price lists are examined.

    Note: The best price Control flags are always per the settings in the customer's own Customer (ibis_sucu) record. For example:

    • This is useful when a chain of stores all share the same pricing. The contract/special price lists only need to be entered under the paying office in the Customers (ibis_sucu) view. Invoices to the stores will check for specials per their paying office. In the following example, price list HOMEDEP contains the special prices for the chain Home Depot. The head office is the paying office and all stores in the chain share the same pricing:

      Customer Paying Office Contracts/Specials in Customers (ibis_sucu)
      HD000-Head Office HD000 HOMEDEP
      HD001-Store 001 HD000  
      HD002-Store 002 HD000  
      HD003-Store 003 HD000  

    • If, however, one of the stores in the chain has special pricing over and above the chain's price list, then you assign NO special price lists to the paying office in the Customers (ibis_sucu) view; instead you put the chain's special price list into every store's the Customer record. Then build a separate special price list for the store with the unique pricing and add it to their Customer record only. Your first instinct might be to leave the chain's price list assigned to the paying office and simply add the price list for the store with the unique pricing to that store's Customer record, but that will not work. When the pricing program sees any special price list assigned in the paying office's Customer record, it looks no further.

      In the following example, price list HOMEDEP contains the special prices for the chain Home Depot. However, store #003 has some special pricing over and above the normal chain prices listed in price list HD003S:

      Customer Paying Office Contracts/Specials in Customers (ibis_sucu)
      HD000-Head Office HD000  
      HD001-Store 001 HD000 HOMEDEP
      HD002-Store 002 HD000 HOMEDEP
      HD003-Store 003 HD000 HOMEDEP, HD003S

    • If the head office is the paying office but they have special pricing not applicable to the stores in the chain, then you need to introduce a new Customer record to act as the paying office only. In the following example, price list HOMEDEP contains the special prices for the chain Home Depot. However, the head office has some special pricing over and above the normal chain prices, listed in price list HD000S. The head office cannot be the paying office because then all the stores would be eligible for the head office special prices; the paying office needs to list no contract/special price lists:

      Customer Paying Office Contracts/Specials in Customers (ibis_sucu)
      HD000-Head Office HDPAY HOMEDEP, HD000S
      HD001-Store 001 HDPAY HOMEDEP
      HD002-Store 002 HDPAY HOMEDEP
      HD003-Store 003 HDPAY HOMEDEP
      HDPAY - Dummy customer to act as Paying Office only HDPAY  

    • If paying offices are 'chained' (meaning if CUSTA paying office = CUSTB and CUSTB paying office = CUSTC) pricing for CUSTA will be per any price lists in CUSTB, not CUSTC.

      Customer Paying Office Contracts/Specials in SU13
      CUSTA CUSTB  
      CUSTB CUSTC CUSTB-S
      CUSTC CUSTC CUSTC-S

      Note: In the example above, an invoice processed for CUSTA will in fact chain down to the last paying office in the chain and will end up in the CUSTC account for the payment.

  1. If the customer has a special price list assigned in Customers (ibis_sucu) and that special is defined as 'Discount Off Master Price', then the discount percent will be applied to the quantity break price according to the order quantity; the customer's pricing level setting the Customers view is not considered. For example, level 1 starts at a quantity of 1 for $17.00, level 2 starts at a quantity of 12 for $15.00 and level 3 starts at a quantity of 144 for $14.00. The customer's pricing level is '3' (meaning they always get the level 3 price). The customer gets 20% off all products. If the order quantity = 1, the order line will be priced at $17.00 less 20% = $13.60, which is better than the quantity break 3 price of $14.00. The pricing routine will not automatically apply the 20% discount to quantity break 3.

  2. If a flyer is in effect but the order quantity is less than the quantity for the flyer's first break point, then the order is not qualified to receive that flyer price. Following the example below from the R1-Pricing & Costs folde in Customer Consolidated Inquiries (ibis_su45), a flyer price of $10.00 will not get assigned unless the customer orders at least 25 units. If less than 25 units are ordered, then the normal quantity break 1 price is assigned.

    Flyer Example
    Customer Consolidated Inquiries/R1 Flyer Example

  3. If a discount on an order detail line is coming from a Special or Contract price list (as assigned in the Customers view) and the user overrides the selling price, the discount is retained and applied to the override price.

  4. If the source code or order type are changed on an order after product detail lines exist, upon completion of the order OE30 will attempt to re-price the detail lines in case pricing is dependent on the new source code or order type.

  Back