By Mark Rockwell, President of Rockton Software and Architect of Rockton Pricing Management (RPM)
When I sit down with a distributor to talk about pricing we often find friction when it comes to handling quantity breaks. The initial description starts out simple: buy more, pay less. Then we start going through it customer by customer, and it’s almost never that simple.
So, let’s walk through what NetSuite does with tiers, where it works, and where we typically see distributors run into trouble.
What NetSuite Does Today
NetSuite has quantity pricing built in, and it’s a reasonable set of tools. You can put quantity breaks on an item, or you can set up a quantity pricing schedule and apply it to a group of items. You can decide whether the discount applies to every unit once you cross the break, or only to the units above it. NetSuite calls that second option marginal rates. And you can decide what counts toward the break: the quantity on the line, the total of that item on the order, everything under a parent item, or everything on the order that’s on the same schedule.
If you have one set of volume breaks and everybody gets them, that’s going to work for you. In my experience, most distributors don’t have one set.
How Many Breaks Do You Need?
A quantity pricing schedule in NetSuite gives you up to four quantity levels above the base price, so you’ve got your price at one, and then four breaks after that.
Now let’s suppose you sell fasteners and you price at 1, 100, 500, 1000, 5000, 10000, and a full pallet. That’s six breaks above the base. What typically happens is somebody creates a second schedule or a second item to cover the rest, and now when the cost changes, you’re updating it in two places. It works, but it’s the kind of thing that catches up with you a year from now when the person who set it up has moved on.
In Rockton Pricing Management (RPM), every item can have its own tier with as many breaks as you need, and you can change them any time you want. We basically don’t store a price for each break. We store the logic of how you get to the price, and RPM calculates it when the line is added to the order.
Is the Tier About This Order, or About the Customer?
NetSuite looks at what’s on the transaction to decide which break applies. If the customer orders 600 units on this order, they get the 500 break. That’s straightforward.
But a lot of the tier deals we see aren’t about the order. They’re about the customer. Let’s say a customer signs an agreement that if they buy $250,000 a year, they get tier 3 pricing on everything. Then they place a $900 order on a Tuesday. On its own, that order is never going to hit tier 3, but the agreement says they get tier 3. So, what happens? Usually a rep overrides the price, or someone sets up a special price level for that customer and has to remember to change it when the agreement changes.
In RPM, we handle that with a filter on the customer. If the customer is assigned tier 3, the tier 3 pricing applies, regardless of the order size. If a customer doesn’t pass the filter, RPM simply ignores that rule and moves on. You set it up once, and when the agreement changes, you change the customer’s tier, not a pile of prices.
Same Item, Different Breaks
In NetSuite, the quantity schedule is attached to the item. You can vary the discount by price level, but the breaks themselves are the same for everybody buying that item.
Here’s a question I like to ask: Do your contractors and your national accounts break at the same quantities? Usually, the answer is no. Contractors might break at 10 and 50. A national account might break at 500 and 2,000. A buying group might want its breaks on dollars instead of units. That’s the same item with three different structures, and every one of them is a real deal somebody negotiated.
In RPM, that’s not a problem. You can build a tier for a customer, a customer group, an item, a category, or a combination of those. Each one only applies to the customers and items that pass its filter, so they don’t step on each other.
What Happens When the Discounts Stack Up
This is where I’d spend the most time if we were sitting down together, so let me walk through the math. Suppose an item costs you $70 and your base price is $100. The customer has a contract price of $90. They order enough to hit the top tier, which takes another 15% off, so now we’re at $76.50. And the item is on a 10% promotion this month. That puts it at $68.85, which is under your $70 cost.
Each of those discounts made sense when somebody set it up, and NetSuite will calculate each step correctly. What it doesn’t do is look at the end result and tell you that line is now below cost. You typically find that out on a margin report after the fact.
RPM runs through every step and then checks the result against a margin floor before the price goes on the order. If it’s under the floor, RPM can hold the price at the floor or send it for approval, whichever way you want it to work. And every line keeps a record of which tier, which contract, and which promotion fired, so if a rep or a customer asks how you got to that price, you can show them each step.
What It Costs to Work Around It
When tiers outgrow the ERP, there are basically three options: a spreadsheet, more price levels, or custom scripts. All three can work. The spreadsheet depends on whoever built it. The price levels keep multiplying. And custom scripts have to be checked, and a lot of times fixed, every time NetSuite puts out a release.
Meanwhile, you have margin going out the door on lines nobody is looking at. In one sample analysis, we found 8.73% in margin that the pricing system wasn’t accounting for. On $100 million in revenue, that’s $8.7 million nobody could see, and you can’t improve margin you can’t see.
How We’d Approach It
RPM doesn’t replace NetSuite. It connects through the API, and when a line is added to an order, RPM calculates the price and fills in the unit price. The way we’d typically get there:
- We sit down with your team and go through every tier you actually use, including the contract tiers and the exceptions that live in somebody’s spreadsheet.
- We build that logic in RPM, along with your margin floors, so it runs on every NetSuite order without anyone touching it.
- From there, you can trace any price back to the rules that built it and see margin by customer, item, and tier.
The end goal is that your Pricing Manager isn’t maintaining tier spreadsheets anymore, your reps can quote without calling the office, and your CFO can see what each tier is earning.
A lot of the companies we work with take this on when they’re moving to NetSuite, when a new CFO starts asking questions about margin, or after a merger leaves them with two sets of tiers to reconcile. If that’s where you are, you’re going to rebuilding your pricing either way.
Let’s Walk Through Yours
If you’ve got a tier structure that doesn’t fit in four breaks, I’d like to see it. Bring the one that gives your team the most trouble, and we’ll walk through how Rockton Pricing Management (RPM), the pricing intelligence platform for ERP-driven distributors, would handle it on a 30-minute discovery call.
Book a Discovery Call

