If customers buy on negotiated or account-specific terms, don’t force legacy deals into broad discount groups. Map the real pricing logic first, then move toward custom price books per account with ERP integration so the storefront reflects real contracts instead of manual approximations.
TL;DR
Legacy pricing deals break when the platform can only approximate them. The fix is not more discount codes or manual review. It’s discovery, pricing logic alignment, custom price books, and ERP integration.
- Don’t force unique contracts into generalized pricing groups.
- Map pricing logic, exceptions, and data ownership before development.
- Use custom price books per account when customers buy on negotiated terms.
- Connect the storefront to the ERP so pricing, terms, inventory, invoices, and reorders reflect the real account relationship.
Why do broad pricing groups fail legacy customers?
A group pricing model recognizes that different customers pay different prices. Group A gets 10% off. Group B gets 30% off. It’s a real improvement. But for most mid-market manufacturers and distributors, it’s a waystation. The group structure approximates the real contracts, and the team fills the gap by hand.
Over the years, pricing complexity grows: volume tiers, contract discounts, freight modifiers, legacy customer adjustments, and promotional overlays. Contracts, terms, and account-specific pricing start breaking the group-discount model.
You can see the ceiling when pricing groups are maintained manually and don’t quite match what accounts were promised. Contract pricing, special terms, and customer-specific items are handled offline or through exceptions. Customer service still fields “why is my price different?” calls.
The bigger the account, the less likely it is to use the site. Key accounts call or email their rep for their price instead of ordering online, so the channel stays stuck serving the customers who matter least.
If those customers do order online, the comments box becomes a shadow system. Customers leave instructions there because the platform can’t capture their complexity: “Apply our negotiated discount.” “Call before shipping.” “Use updated PO terms.” Each comment requires human review. Customer service becomes the bridge between intention and execution.
One supervisor captured the situation perfectly: “We’ve gotten really good at cleaning up after the system.” That is not a failure of talent. It is a misallocation of it.
What does manual pricing exception handling cost?
Orders placed through the platform don’t move cleanly into the ERP. They enter a queue for review. Customer service checks for pricing mismatches, missing data fields, contract exceptions, and free-form comments left in the order notes.
Three to five minutes per order. That feels harmless. But multiplied across thousands of orders, it consumes full-time equivalents.
In mid-market companies, friction is often absorbed rather than eliminated. Customer service absorbs manual corrections. Sales absorbs clarification calls. Operations absorbs rework. Finance absorbs credits. IT absorbs troubleshooting. Because each department owns only part of the pain, no one aggregates it.
When someone finally asked what the annual cost of this friction was, the room grew quiet. Between customer service overtime, finance correction processing, sales clarification time, and IT troubleshooting, the total exceeded $600,000 per year.
The postponed integration project had been estimated at roughly the same number. For over a year, leadership had scrutinized the visible project cost while absorbing an equivalent cost inside operations. The money had been leaving the business either way.
Where is our legacy pricing logic actually stored?
To fix legacy pricing, you first have to find it. In one account-specific pricing environment, the ERP handled part of it. The rest lived in spreadsheets.
Uncle Bob’s spreadsheets.
They are intricate. Thoughtful. Layered. Tabs built over years of exception handling. Formulas nested inside formulas. Conditional logic reflecting real-world nuance.
When finance sees a margin anomaly, they call Bob. When sales questions contract pricing, they call Bob. When the commerce team wants to expose pricing online, they sit beside Bob to understand how it really works. He is patient. He explains verbally. Onboarding a new analyst requires months of shadowing. Not because Bob is secretive, but because his knowledge is contextual. It lives in experience. In hallway conversation.
One afternoon during a strategic planning session, someone asked casually, “What happens when Bob retires?” All eyes wide, but no mouths moved.
That creates quiet risk. For IT, every integration that touches that knowledge is fragile. For the CFO, key-person dependency creates financial exposure that doesn’t appear on any report. For the CEO, it is a valuation risk. Enterprise value shouldn’t depend on one individual’s availability.
What should we map before changing our pricing system?
Nothing exposes the true condition of an ERP like digital transformation. Pricing logic, approvals, exceptions, unit rules, and contract structures all become visible. You see the one-off decisions, shortcuts, and tribal knowledge the business has quietly relied on.
None of this is a deal breaker. But it’s reality. And reality revealed early is far cheaper than reality revealed halfway through a build.
This is not about blame. It’s about clarity. Clarity protects you from downstream pain.
At The B2B eCommerce Agency, we start with diagnostic and discovery work to define the pricing, ERP, and workflow reality before re-platforming. Discovery is essential here. Integration, pricing logic, and data ownership decisions made in the wrong order are the most expensive mistakes we see.
Skipping alignment is the cheapest mistake up front and the most expensive one at the end. When teams rush past it, they pick platforms for the wrong reasons. They digitize broken workflows. ERP limitations surface in the worst moment. Features get redesigned multiple times.
Do not estimate against undocumented assumptions. If it isn’t a labeled finding, it isn’t ready to price.
What is the right pricing model for account-specific deals?
Stages are ordered by capability, but companies don’t have to climb them one rung at a time. The right target is the stage that fits how the business actually sells. Fit over ambition.
Many companies move to group or tier pricing because it is the easiest next step. But for companies whose customers buy on negotiated or account-specific pricing, the stronger move is directly to custom price books per account and real ERP integration, instead of building a list-price store and rebuilding it later.
The trigger to move is when customers need real account pricing, invoices, and reorders, and the team is tired of patching it manually.
This is the hard move because the storefront has to reflect the actual account relationship, not an approximation of it. Require the new system to support:
- Custom price books per account.
- Real ERP integration so the ERP and storefront talk to each other.
- Pricing, terms, inventory, order history, and invoices that reflect the actual account relationship.
- Fewer discount codes, credits, and manual invoice adjustments to make online orders match agreements.
- Less re-keying or correction in the ERP after the fact.
Measure whether the new system reduces review queues, pricing mismatch calls, free-form checkout instructions, and manual ERP corrections. If those problems remain, the pricing model is still being patched by hand.
When the group model has done its job, it’s time to move. The goal is to make the next build the last rebuild.
Align the team before you rebuild pricing
You can’t fix a structural problem with an unaligned team. In one $160 million distributor, a modernization project stalled because priorities were misaligned.
Sales wanted pricing flexibility preserved. Finance wanted pricing governance tightened. Operations wanted fewer custom exceptions. IT wanted fixed requirements to avoid scope creep. Marketing wanted a clean launch narrative.
No one was wrong. But no one had agreed on trade-offs.
Make the hard decisions explicitly with your leadership team:
- Are we prioritizing flexibility or enforcement?
- Are we willing to reduce manual exceptions to gain scale?
- Are we willing to change compensation structures to drive adoption?
If these decisions aren’t made explicitly, they are made implicitly in hallway conversations and delayed meetings. Every feature becomes a debate. Every integration becomes a negotiation. Momentum slows.
Start by naming the pricing reality. Then build the system around that reality.
Frequently Asked Questions
Why do our biggest accounts still bypass the portal and call sales for pricing?
How do we justify ERP integration if the project cost looks too high?
Should we keep expanding discount groups or move to account-specific price books?
What has to be decided before we rebuild our pricing system?
Don't forget to share this post!
Ethan Giffin
Ethan Giffin is a trusted advisor to mid-market manufacturers and distributors navigating digital modernization. For nearly two decades, he has helped executive teams eliminate structural revenue leakage, align leadership around a shared commercial vision, and modernize how they sell without destabilizing what already works.He is the author of Closing the Digital Revenue Gap: 10 Revenue Blind Spots That Are Costing You More Than You Think, a practical guide that exposes the hidden costs buried inside manual workflows, disconnected systems, and adoption failures. His work reframes digital transformation as margin protection and revenue velocity — not a technology initiative, but a business operating decision.
As Founder and CEO of The B2B eCommerce Agency, Ethan has guided companies through complex eCommerce and systems transformations in the era of Industry 4.0. His approach focuses on sequence, alignment, and adoption — because launch doesn’t create value. Adoption does.
An international speaker and host of the B2B eCommerce Summit, Ethan convenes executive leaders shaping the future of B2B commerce — and equips them to close the digital revenue gap before it quietly limits scale.