Overview of Pricing in coreFORCE

As an enterprise level software package, coreFORCE includes a lot of layers that you can utilize when setting the pricing for your website. This article will give an overview of some of these pricing features.

Related Articles

In general, most of the pricing for your website will be taken care of by setting up Pricing Structures. 

Understanding Pricing Structure in coreFORCE.

You can also follow this link if you'd like more detail about MAP in coreFORCE:

Setting up MAP and Resolving Violations

Overview of Priority

Minimum Price

Minimum Price is the actual minimum that you will agree to sell an item for. The pricing structure shouldn't ever calculate a price below the minimum price. Additionally, the Pricing Structure doesn’t actually override the minimum; but it will almost never price things at the minimum unless your Pricing Structure is set incorrectly (such as a markup of 1%).

List Price 

This is usually MSRP. This is often set by the distributors in their feed.

*Minimum Price and List Price do NOT override the Pricing Structure. They are part of the data the pricing structure uses to calculate the sale price.*

Product Sale Price

Setting a price here (in the grid at the bottom of the pricing tab) will have the highest priority. You can do a few things here:

• Set a price for a specific user-type
• Select a Start and End date (if you're running a week long promotion for example)
• Set a Location (This will be explained in more detail below)
• End this sales price after X amount sold

  • End after X sales must have a start date. If the start date is empty, you are telling the system that after X sales from all time. When you put a start date in, the sales are from beginning of the day of that date. So, a sale as 12:01am on that day will count as a sale toward X.

• Set a price for the sale

Example of Product Sale Price:

Location Drop Down for Product Sales Price

It is important to note that "If a location is set, a product price of type "Sale Price" will only be valid for inventory from that location."

The Location Dropdown was designed for specials.

Example:

We have 10 of these at location X… we’re going to sell them for 20% off, but we don’t want to sell distributor inventory at 20% off.

For any other situation, you don’t want to set a location or else you’ll likely have unexpected results when the product goes out of stock. To avoid this, you could also set the "End after X Sales" field to whatever your in-store inventory is. 

Other Related Articles:

Set a Shipping Charge for a Specific Product in coreFORCE

User Based Pricing in coreFORCE

Add a Surcharge to All Products in a Category

How to configure MAP pricing to meet manufacturer requirements

If you have any further questions, please submit a ticket to our Help Desk.