Line Items

This page covers the Products area inside a project: adding a new item, configuring it, handling validation issues, and understanding when Tempr recalculates pricing.

How the pricing engine works

Tempr sources it's pricing data from a combination of different sources, including:

Tempr

• Metro Screenworks
• Vantis Smart Film
• Austin Custom Screens
• Dallas Flat Glass
• Window Films

PIC Business ERP

• Hunter Douglas
• Alta Window Fashions
• MagnaTrack

Parable CPQ

• Eclipse Shading Systems
• Vantis Shade Systems (except SmartFilm)

SynthX CPQ

• Future Use

Where To Add Items

Internal users add line items from the project's Products area.

Use the Add Item action to create one or more new item rows.

Add Item Flow

When adding an item, Tempr asks for:

• Vendor
• Product
• Quantity
• Model for PIC-driven items

Each new row is stored as a project measurement. That record carries the product class, configuration data, pricing data, approval state, and validation output used later in proposals and operations.

What Red Item Lines Mean

If an item row appears red in the products table, that item has one or more product-level errors.

To view the relavent errors, click the Errors button on the right side of the row to open the error panel.

Tempr highlights the row red when the underlying product reports errors, such as:

• PIC validation faults
• PIC error messages returned from validation
• Parable validation errors
• matrix or pricing failures on Tempr-native items
• product-specific configuration problems raised by the pricebook logic

Use the Errors action on that row to open the full error list.

Pricing Basics

Each item stores its own pricing snapshot, including:

• cost
• MSRP
• sell price
• taxable flag
• labor values
• item-level discounts

Tempr builds that pricing snapshot from the item's current pricebook calculation or adapter result and saves it on the item.

When Pricing Recalculates

Tempr recalculates item pricing after actions that can change the product's real cost or sell price.

Common examples:

• saving a Tempr-native configuration panel
• saving a Parable CPQ panel
• validating a PIC item
• using Reset Pricing
• copying an item into a new project context

When Tempr resets pricing, it clears the saved pricing payload first and then rebuilds it from the latest available pricing source.

Resets Remove Saved Item Discounts

This matters because item-level discounts are stored inside the item's saved pricing payload.

When pricing is reset:

• Tempr clears the saved pricing data
• Tempr rebuilds pricing from the current pricebook or adapter response
• item-level discounts stored on that pricing snapshot are removed unless a user reapplies them

This is why a user can see discounts disappear after reconfiguring a product or manually resetting pricing.

Expired Quotes And Repricing

If a vendor quote or imported price is no longer current, treat repricing the item the same way operationally as a pricing reset:

• the old saved pricing should no longer be trusted
• Tempr should be expected to rebuild pricing from current data
• saved item-level discounts may need to be re-entered

The safe rule for users is simple: if a quote was reset, refreshed, or has expired, review pricing and discounts again before moving the project forward.

Best Practices

• finish product configuration before applying manual item discounts whenever possible
• do not ignore red item lines; open the error panel and fix the root cause
• for PIC items, wait for successful validation before trusting pricing
• for Parable items, save from the Parable CPQ modal so Tempr captures the latest dealer cost and validation state
• after any pricing reset or quote refresh, re-check discounts and minimum-to-start totals