Three numbers from the room first. At the P21WWUG pricing session on September 10, among attendees who responded to the live polls (n=30–32 per question):
57% said they have no reason-code field or Alert Maintenance rule tracking pricing overrides.
59% either hadn't reviewed their product-group pricing in over a year or don't price at that level at all.
33%, one in three, could name the owner of every price library they run.
None of that is a P21 problem. P21 gives you near-total freedom to build pricing however you want. That freedom is why, a few years in, one person ends up holding a structure of libraries, books and pages that nobody else fully understands, and why a single vendor cost increase turns into two days of manual work and hoping nothing gets missed. It's a structure problem, and structure is fixable.
Here are three of the six patterns we walked through live, and what to check in your own system.
One rule, one multiplier, covering an entire product group, whether or not the SKUs inside it behave the same way. A $4 utility blade and a $180 carbide end mill sitting in the same "Cutting Tools" group both price at exactly 30% over cost. Fast to set up. Blind to how differently those two items should be priced.
Check it yourself: pull your current price pages by product group. For any group still on a single flat method, look at how much the SKUs inside it vary in cost or value. If a low-cost commodity part and a high-value specialty item carry the same markup, that's where margin is likely sitting uncaptured.
Libraries pile up over the years, one customer or one promotion at a time, with no plan behind the accumulation. A library named for a temporary Q3 deal three years ago is still active today, and nobody on staff can say why. Nothing about that shows up as an error. It sits there, eligible to price a transaction, until someone happens to notice.
Check it yourself: pull your price libraries and sort by last-reviewed date. Flag anything with no assigned owner, no naming convention, or no review in the last 12 months. If a library is stale and no customer is actively priced off it, it's a candidate for retirement.
A rep overrides a price by hand. The transaction saves. Nothing captures why. Multiply that across a sales team over months, and the pattern, not any single override, is what costs margin, because there's no record connecting the override to a reason anyone could review later.
Check it yourself: check whether your order-entry screens have a reason-code field for price overrides. If not, that's the first build. Then check whether Alert Maintenance has a rule that fires when entered price drops meaningfully below system price. Both are same-day configurations using tools already in your P21 license, no add-on required.
Price Matching Conflicts: the wrong resolution rule silently letting an old discount outrank pricing you built specifically for that item
Contract Controls: an expired contract still marked active, quietly blocking better pricing underneath it
Cost Isolation: pricing off master cost when a branch's real landed cost is meaningfully different.
Everything in this post, you can check yourself this week.
For the full picture, all six themes, a tiered fix path for beginner, intermediate, and expert levels, and a complete menu of options once you've diagnosed the problem, it's all inside the P21 Pricing Architecture Playbook.
With 30+ years in distribution and nearly a decade of developing and deploying Machine Learning models tailored specifically for distributors, he helps mid-market industrial distributors identify and eliminate margin leakage across pricing, costs, and inventory — and keep it fixed. He built Intuilize on the premise that software alone doesn't earn trust and expertise alone doesn't scale: distributors need both a model built for their business and someone who knows distribution well enough to drive adoption and deliver real ROI
Contact: nelson@intuilize.com | LinkedIn