Pricing Tips

Owned by Loan Thai
Apr 12, 2023
3 min read



  • There is a template detail ID on both the OrderLine and OrderInvoiceLineprice tables.

  • The ID on the OrderLine corresponds to the template detail that was used to populate the item onto the order. It has nothing to do with whether or not that’s where the pricing came from.

  • The ID on OrderInvoiceLinePrice is where the pricing for the line came from and has nothing to do with how the item got on the order.

  • Simply put the ID on the OrderLine is where the item is loaded from, and the ID on the OrderInvoiceLinePrice is where the item is priced from.

  • They could be the same and they could be different depending on whether or not pricing is coming from a Super Customer or Price Group template.

  • There should always be at least one OrderInvoiceLinePrice record that corresponds with every OrderLine.

  • There can only be 1 OrderInvoiceLinePrice per OrderLine with a PriceTypeID of 1 through 6.

  • However, there can be multiple OrderInvoiceLinePrice records with a PriceTypeID of 7.

  • The PriceTypes are defined as follows:

    • 1 = Spot Fixed

    • 2 = Spot Market

    • 3 = Template Fixed

    • 4 = Template Market

    • 5 = Special Fixed (Price comes from a template but includes a special contract)

    • 6 = Special Market (Price comes from a template but includes a special contract)

    • 7 = Feature (Added pricing to an order line that comes from a feature price contract)

  • There are two types of Contract Pricing, Feature, and Special.

  • Feature pricing acts as an added price to whatever the normal unit price would be. Thus multiple feature contracts can exist for the same order line.

  • Special pricing acts as a differential override. Only one special contract can be used for a single order line and will override any differential that might normally come from a template.

  • If a price has been keyed into the Unit Price field on the order line or the Unit Price field in the dollar dropdown, the PriceTypeID will change to 1 and any Alt UoM information will be wiped out.

  • If any part of template market pricing is changed in the dollar dropdown and the blue save button is clicked, the PriceTypeID will change to 2 and any Alt UoM information will be wiped out. Alt UoM is only a function of template pricing.

  • There are two automated ways in which an item on an order can be priced. These are the Re-calc and Re-Price functions. At the time that an order is opened in Customer Order or Retrieved in Logistics Maintenance, the software will attempt a Re-calc of any items for which the firm price flag is not set. This function uses whatever pricing information already exists on the OrderInvoiceLinePrice record and looks for any available pricing. For example, if an item comes from a template using market pricing and the price wasn’t available at the time the order was created, the re-calc will use the same market information and look to see if a market price is now available. The Re-price function must be initiated by the user either by clicking Re-Price in the Customer Order Ribbon Bar or by right click Re-pricing in Logistics Maintenance. This function will ignore any existing pricing information  on the OrderInvoiceLinePrice record and re-create it with whatever appropriate pricing information is available. The Re-Price function ignores the firm price flag for whatever price types are selected in the Re-Price prompt.

  • “Re-Pricing” Orders through Logistics Maintenance causes the OrderInvoiceLinePrice records to be deleted and re-created.

  • Re-pricing through the Customer Order screen updates the OrderInvoiceLinePrice records rather than deleting and re-creating them.

  • Querying the view, vwAudit_OrderInvoiceLinePrice_Deleted can be helpful in determining whether or not a user called for a Re-Price through Logistics Maintenance.

  • This view can be queried by any of the columns in the OrderInvoiceLinePrice table. Generally OrdLineSeqno or Ordseqno are the best columns to use in your query.

  • There are three possible places that template pricing can come from, Customer, Super Customer, or Price Group templates.

  • When pricing an item from templates the system will first look for a Customer Template. If no valid template exists or pricing is not defined on the customer template, the system will look for a Super Customer template. If no valid template exists or pricing is not defined on the Super Customer template, then the system will look for a Price Group template. 

  • This hierarchy will be used separately for determining which items to load as well as which price to use. For example, you might have items that load from a Customer template but the pricing comes from a Super Customer or Price Group template.