# Put every customer 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. Source: https://revomo.ai/solutions/price-lists-customer-specific-pricing/ --- Solutions · Price lists & customer-specific pricing ## 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. [See Revomo in action](https://revomo.ai/contact/)[Assess your margin opportunity](https://revomo.ai/margin-assessment/) 1 spine Base, market & customer lists on one hierarchy <24 hrs To update every list a change touches 5–10 days First module live · full go-live 6–10 wks The problem ### Customer-specific pricing, managed in spreadsheets, is a full-time leak. Nobody knows which price governs “Which list is he on?” Base list, market list, customer book, honored quote, four candidate prices per order, and the ERP picks one without showing its work. List maintenance is a manual grind “Every customer price is a snowflake in a spreadsheet.” Thousands of customer-specific prices maintained by hand means updates take weeks and errors ship as invoices. New lists ship, old prices keep flowing “The update went out; the old prices kept shipping.” Without governed versions and effective dates, downstream systems serve stale prices for weeks after every change. Price book explorer, AL-EXT-240 down the hierarchy 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 SKU, resolved base → market → customer. The winning record is cited on the price, not implied by whichever spreadsheet is newest. Illustrative preview · not connected to live data RV·2026·S8 · The hierarchy ### 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 RV·2026·S8 · Change with control ### 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 List-wide price change: PL-MKT-AH-DIST Scope ✓ Rule ✓ Preview Publish SCOPE **Northeast Distribution market list** 1,842 SKUs · 184 customers inherit RULE **List +3.0% · round to nearest $0.50** Effective Oct 1 · corridor floors enforced PREVIEW **What actually changes** 1,791 SKUs updated · 37 contract-protected held to term · 14 clamped at corridor floor every held-out and clamped SKU listed with its governing record Stage for approval Illustrative preview · not connected to live data List versions & publishing: PL-MKT-AH-DIST **v2026.5 · staged** +3.0% list change · effective Oct 1 · approved by pricing owner Awaiting publish *publishes on eff. date* **v2026.4 · active** 1,842 SKUs · in force since Jul 1 Active *governing today* **v2026.3 · archived** retired Jul 1 · full history retained *audit trail* ERP synced 2m ago · CRM synced 2m ago · customer portal synced 2m ago Old prices stop shipping the day new ones start, because every downstream system reads the same version. Illustrative preview · not connected to live data RV·2026·S8 · Versions & publishing ### 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 How it runs ### From price-list chaos to a governed hierarchy Step 01 **Load the lists** Your base, market and customer lists land on the spine, overlaps and conflicts surfaced on day one. [Data & Context Studio →](https://revomo.ai/platform/#data-context-studio) Step 02 **Govern the hierarchy** Precedence becomes explicit; changes run scope → rule → preview → publish with approvals on the record. [Price Management →](https://revomo.ai/platform/#price-management) Step 03 **Serve every channel** Resolved prices flow to quotes, orders and the portal from one version, guidance included. [Quote Management →](https://revomo.ai/platform/#quote-management) FAQ ### 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. [See Revomo in action](https://revomo.ai/contact/)[Assess your margin opportunity](https://revomo.ai/margin-assessment/) Plate S8 · Series 2026 · Solutions · RV·2026·S8