Every customer’s price,
on the record.
Base lists, market lists and customer price books resolve on one governed hierarchy, so every price cites the record that governs it, and updates reach every system the day they take effect.
Customer-specific pricing, managed in spreadsheets, is a full-time leak.
| Level | Price | Governing record | |
|---|---|---|---|
| Base list | $210.00 | PB-BASE-2026 · v2026.4 | |
| ↳ Market list · Northeast Distribution | $201.60 | PL-MKT-AH-DIST · −4.0% | |
| ↳ Customer · Summit Building Supply | $198.00 | CTR-2087 §4.2 | Governs |
| ↳ Quote override | , | None active |
One price, resolved down the hierarchy
Every SKU resolves base → market → customer → quote, with the governing record cited at each level. Customer-specific prices stop being snowflakes and become rules the spine maintains.
- Base, market and customer lists with explicit precedence
- The winning record cited on every resolved price
- Customer-specific terms maintained as rules, not rows
A list-wide change without the spreadsheet weekend
Scope, rule, preview, publish. The preview shows exactly what changes, and exactly what doesn’t: contract-protected items held to term, floors enforced, every exception named.
- Scope by list, segment or attribute, thousands of SKUs at once
- Preview the full impact before anything ships
- Protected items and floor clamps handled by rule
New prices start, old prices stop, same day
Lists are versioned records with effective dates. The staged version publishes to ERP, CRM and the customer portal in one motion, and the old one retires itself.
- Versioned lists with staged effective dates
- One publish reaches every downstream system
- Full version history for the next audit or dispute
From price-list chaos to a governed hierarchy
The questions pricing ops asks first
We have tens of thousands of customer-specific prices. Does that migrate?
Yes, loading your existing lists is the first step, and the spine flags the overlaps and contradictions your spreadsheets have been hiding. Most teams find the cleanup alone pays for the project.
Can sales still negotiate customer-specific prices?
Yes, through quotes and agreements that land on the same hierarchy, with corridor guidance at the moment of negotiation. What ends is the untracked spreadsheet edit that nobody can explain later.
What happens in the ERP?
The ERP keeps executing orders, it just reads prices the spine resolved and published, instead of maintaining its own competing copy. Sync is continuous and versioned.
Put every price on the record.
Bring your messiest price list. We’ll show you the hierarchy, the conflicts and the first governed update.