Scenario

TechNest, a mid-market SaaS provider of enterprise collaboration tools, operates a multi-tier sales model:

• Sales Reps can offer limited discounts.
• Managers and VPs can approve deeper discounts for strategic accounts.

However, rather than approving based on a discount percentage, TechNest sets absolute floor prices per SKU. For example, while the list price for the “Collaboration Suite Pro” is $100/user/month, Sales Reps must not go below $80, and Managers must not approve less than $70.

DealHub’s standard approval workflows rely on discount percentage thresholds—not specific price points.

To meet this requirement the team implemented a flexible floor-price-based approval system using DealHub’s product and proposal attributes, assignment rules, and general workflows, outlined below.

Solution

PRODUCT ATTRIBUTE

1. In Products, click on Actions, then click on Settings, then select the “Product Attributes" tab. 
2. Click Add Attribute and change Type to “Number”

3. Label this attribute “Floor Price”
   1. Note, you can create as many of these “Floor Price” levels as you need. For example, if you have a floor price for sales and a different one for managers, you can create two (2) separate Attributes.

4. After saving the new attributes, populate their values. You can do this manually by double clicking on each product, or by using DealHub’s excel bulk export/import functionality.

PROPOSAL ATTRIBUTE 

1. In Products, click on Actions, then click on Settings, then select the “Proposal Attributes" tab. 
2. Click Add Attribute and change Type to “Currency.”
3. Label this attribute: “Floor Price Difference.” Mark as read only and hidden. 
   1. Note: Create as many of these proposal attributes per floor price type. For example, if you have a floor price for sales reps and another floor price for managers, create 2 proposal attributes: “Floor Price Difference - Sales Rep” and “Floor Price Difference - Manager”

4. In the assignment rules of each product, find the new proposal attributes you created for the floor prices and enter in the following formula in the field: eItem.net_price] - ProductAttribute.Floor_Price] 
   1. *Please note that the Product Attribute field should be the one that matches your proposal attribute. For example, if you’re filling in information for the Floor Price Difference - Manager proposal attribute, then your formula would be: aItem.net_price] - rmatching proposal attribute for manager floor price]

TAG

1. Add the Tag “Floor Price” to all of your products that will be affected by the floor price approval workflow.

APPROVAL WORKFLOW

1. In Approval Workflow & Validations → General Workflows, create a new workflow with the following settings:
   1. Description: Floor Pricing rinsert role of pricing floor]
      1. Example: Floor Pricing Sales Rep OR Floor Pricing Manager
   2. Active when: true
   3. Approval value:
      1. Note: Use the total proposal attribute for the floor price difference proposal attribute that matches the role in your description. So if you wrote Floor Price Sales Rep in the description, use the Floor Price Difference Sales Rep proposal attribute total here.
   4. Direction: Descending
   5. Immediately present for approval to all levels: TRUE
   6. Evaluate each product separately: TRUE
   7. Roles:
      1. Set your first row’s role to the role of the floor price (Description = Sales Rep, Role = Sales Rep)
      2. Add the “floor price” tag to the table via the “Add Tag” button
      3. Mark the first row as 0 under the Tag “Floor Price”
      4. Mark the last row of the table as -99999999999