Any updates on this as we are deciding whether or not to utilize repairshopr. Coming from a system that had 3 price levels and the ability to set discounts per customer is pretty important to us.

Something that complements this also is this idea that published several days ago:

When we enter the cost and the retail price the system gives us a percentage markup, imagine that we can place a markup and based on the cost the system system calculates a price that maintains our % desired margin. We all know how variant the market is today buying prices vary like crazy, and each time we have to be checking if we are working with the correct prices and manually change them. Then the flow would be like this: In each item or service we mark a desired markup or % of desired margin, when we get an order to receive it into our inventory we introduce the purchase cost and as we have set the desired % it will calculate the price automatically.

Copying my post that had less votes and redirecting new votes to here:

-----------------
Pricing Fields for Inventory/Products: MSRP/Retail, Sale/Override, Customer Price, Company Cost
-----------------

There are more $$$ fields than just price and cost for most product and inventory items. Obviously, Price and Cost are both equally important, but there's also other factors that heavily influence purchasing decisions in the retail and service industry. The two main ones that come to mind are MSRP/RETAIL pricing and SALE/DISCOUNT pricing.

What do customers hate the thought of? Paying FULL PRICE for something! That's why you /show/ them the msrp/retail price, so they know they're NOT paying it. On top of just showing the customer this information, it's infinitely helpful being able to reference these details when working with inventory. We're constantly having to look up the msrp of products we sell, because we don't have a defined field to put that information in on the product page in RS.

What do customers LOVE the thought of? SAVING MONEY! That's why if you are offering products/services below msrp, you want to /show/ the customer how much money you're SAVING them. Adding the "Sale" price field would both make your customer happier (on the psychological side) and would allow us to more easily have sporadic sales and discounts, where we can easily make a temporary price change to a product (including non-serialized inventory) and then change it back without losing our normal reference price.

Simple, simple, simple implementation: Just add "MSRP/Retail Price" and "Sale/Discount Price" fields to the already existing "Customer Price" and "Company Cost" fields in products. MRSP/Retail would just be a reference point for customers and staff, and Sale/Discount (if set) would override the Customer Price. These additions would NOT clash with existing settings, or change anything RS users currently have setup, if the fields are added and start out as blank.

* Call the idea police! We've got ideas coming from left and right over here! *

Along with this, it would also be very helpful to have an "MSRP" price. This would be mainly for internal reference, but would also show on estimates/invoices (with a strikethrough) to show the customer how much we are below retail (even if it's only like $19.99 MSRP compared to $19.95 retail). Perceived value matters to the customer!

In all, there should be a customizable number of pricing tiers (1, 2, 3, etc) and we'd be able to "label" the tiers for reference (MSRP, Retail, B2B, Partner, Wholesale, Employee, Cost, etc).

I have always wanted this too. There are several ways I could use that type of pricing structure.

I've been after this for ages! It would be nice to assign a customer a price level too.

Even better if someone can go on a rate for parts and a rate for labour too.... but anything this direction would be great!

Yes I'm in the midst of how to sort out 5 pricing levels we have per product. Were currently having to do it all via excel sheet reference!