Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

B2B Pricing Engine in Your ERP: Price Lists, Discounts and Framework Agreements

Price resolution hierarchy, discounts, framework agreements, governance and e-invoicing: how to configure B2B pricing in your ERP without drowning in exceptions.

B2B Pricing Engine in Your ERP: Price Lists, Discounts and Framework Agreements

In most mid-market trading, manufacturing and distribution companies, the selling price is not a data point: it is a permanent negotiation. One customer has a price agreed with the salesperson, another enjoys a historical discount nobody can justify, a third depends on a framework agreement signed two years ago. If the ERP cannot carry that complexity, it migrates elsewhere: into Excel files, emails and order comments. And the day management asks “what price do we really sell at?”, nobody can answer with certainty.

This guide is for CFOs, sales directors and CIOs who want to govern selling prices inside the ERP: understand how a pricing engine decides, how the main vendors model the topic, and how to implement it without multiplying exceptions. The functional descriptions rely on the vendors’ official documentation, cited throughout. No margin or savings figure is put forward: the numbers that follow are teaching examples.

Why Prices Drift: Manual Exceptions, Shadow Spreadsheets, Invisible Margins

Pricing drift almost always follows the same three-step pattern.

1. The exception becomes the rule. To close a deal, a salesperson obtains a special price. With no simple mechanism in the ERP, order administration keys the price by hand on the order line. The price exists on that one document only: the next order starts again from the standard list price, and the customer complains.

2. The shadow file moves in. To avoid mistakes, an order administrator keeps a “customer prices” workbook. It becomes the real source of truth, but nobody else controls it, it has no end date and no history, and it disappears with the person who maintains it.

3. Margin becomes invisible. Discounts pile up (line discount, invoice-level discount, year-end rebate) and nobody calculates the real net price. Margin leaks, what the literature calls price leakage, are no longer visible line by line, only at year-end, when it is too late to renegotiate.

The common thread: the price is not governed, it is endured. A well-configured pricing engine does not remove negotiation, it gives it a framework: every price has an origin, a validity period, an owner and a trail.

To read profitability once prices are set, see our article on managing customer margin in the ERP.

Anatomy of an ERP Pricing Engine

Whatever the vendor, a pricing engine answers one question: for this customer, this product, this quantity, this day, this channel, which price and which discounts? It does so by combining a hierarchy of rules with a set of dimensions.

Resolution Hierarchy

The central principle is the resolution order: when several prices could apply, the engine picks the most specific one. A common B2B hierarchy:

  1. Contract price (framework agreement or negotiated deal, specific customer and item);
  2. Customer price list (pricing specific to that account);
  3. Customer group price list (customer family, segment, chain);
  4. Standard price (list price or base price).

This order must be explicit, documented and identical across all channels. Two salespeople should never get two different prices for the same situation depending on how they key the order. During scoping, ask the integrator to show you, on a real case, which rule won and why: a good engine can explain it line by line.

Dimensions: Currency, Quantity, Validity Period, Channel, Sales Unit

The hierarchy answers “who”; the dimensions answer “under what conditions”:

  • Currency: a price list is often tied to a currency; Odoo’s documentation, for example, provides for one currency per price list (Odoo documentation, pricelists). Decide whether you manage fixed prices per currency or a conversion rate applied to a reference price: the impact on exchange differences is not the same.
  • Quantity: volume tiers (from X units, this price). Specify whether the tier is assessed per line, per order or cumulatively over the period.
  • Validity period: start and end date. Without an end date, a commercial condition stays active indefinitely. This is the leading cause of stale prices.
  • Channel: order desk, field sales, EDI, B2B portal, e-commerce. A price can legitimately differ by channel, but that difference must be intended and configured, not the result of an engine that only applies on one channel out of three.
  • Sales unit: stock unit, sales unit, packaging unit (piece, carton, pallet). A carton price applied to a single piece is a classic mistake in the first weeks of production.

Discounts: Line, Invoice-Level, Volume, Year-End Rebates

Discounts form a second layer, often poorly separated from the price:

  • Line discount: a percentage or amount on a line, triggered by a condition (customer, item family, quantity).
  • Invoice-level discount: applied to the total (for example a prompt-payment discount or an end-of-order discount).
  • Volume discount: triggered by a quantity or amount threshold.
  • Year-end rebates and back-end discounts: calculated after the fact, on the period’s revenue. They do not appear on the invoice and are handled through accrual then credit note. This is the territory of trade promotion management, which we detail in the article on TPM, deductions and rebates.

A useful design rule: separate the price from the discount. A negotiated price of 92 instead of a list price of 100 can be configured either as a net price (92) or as an 8% discount. Both give the same amount, but not the same readability: the discount preserves the reference list price, useful for measuring the commercial concession granted, while the net price is more stable when the standard list price changes. Pick one convention and stick to it.

How SAP, Dynamics 365, Odoo and Sage X3 Model Pricing

The four vendors below cover most of the mid-market projects we see. This table describes modeling logics, not a ranking: the right approach depends on your pricing complexity, not on a league table.

VendorCore conceptResolution logicPoints of attention
SAP (S/4HANA, ECC)Condition technique: condition types, condition tables, access sequences, pricing procedureThe access sequence sets the search order of valid condition records; the pricing procedure orders the condition types (SAP Learning, condition technique)Very powerful and highly configurable; requires real expertise to stay maintainable
Dynamics 365 (Supply Chain Management)Trade agreements entered in price/discount journals, price groupsSales prices by item, customer, customer group or all customers; journals let you prepare, then validate before posting (Microsoft Learn, trade agreements)The journal-based approval flow is a governance asset; unified pricing management (Microsoft Learn, price groups) is evolving, so check the deployed version
OdooPricelists with rules: fixed price, discount or formulaPricelist assigned to the contact, rules with minimum quantity and validity period (Odoo documentation)Easy to pick up; the documentation does not detail arbitration between competing rules, so test your edge cases
Sage X3Price lists by structure: discount and charge columns, grouped listsA list structure determines the conditions managed per document line (Sage X3 online help, structures)Grouping rules (a grouped list excludes the others) and structure-change rules must be mastered before configuring

Three practical lessons:

  • The more flexible the tool, the more discipline matters. SAP’s condition technique allows almost anything; without naming conventions and record reviews, it produces a mille-feuille.
  • A simple engine is not a poor engine. Odoo’s pricelists cover a large share of a trading mid-market company’s needs. Limits appear on complex cascades (range discount, then volume, then contractual).
  • Test your most twisted case, not the demo. Ask the vendor or integrator to reproduce in a sandbox a customer with a contract, a volume discount and a simultaneous promotion. For the question grid, see our ERP demo evaluation guide and the comparison of ERP features for wholesale.

Framework Agreements and Negotiated Prices: Lifecycle, Expiry, Indexation

A framework agreement sets conditions (prices, discounts, volumes) over a period, within which call-off orders are placed. In the ERP, it becomes the highest-priority level of the hierarchy. Its lifecycle must be managed like a business object, not as a mere price-list line:

  1. Creation: link to the customer, items, committed volumes and delivery terms, with the signed contract attached.
  2. Validation: approval based on the margin threshold (see governance below) before activation.
  3. Consumption tracking: quantity or amount consumed against the commitment, with alerts on under-consumption or overrun.
  4. Expiry: alert before the end date, explicit decision (renew, renegotiate, stop). Without it, an expired contract price keeps applying, or conversely silently falls back to the standard price and surprises the customer.
  5. Indexation: periodic review according to a formula (index, cap, floor). Formula mechanics, retroactivity and accounting are covered in our article on price revision and indexation clauses.

Retroactivity. Does a price change apply to orders already entered but not delivered? To deliveries already made but not invoiced? These rules must be settled in writing: it is the number one source of billing disputes. The healthiest convention is to freeze the price at the order date (or delivery date, depending on your contract) and allow a recalculation only through a traced action.

Link with CPQ. When the product is configurable and the quote requires complex calculation, a configure-price-quote (CPQ) tool is added to the ERP. The ERP pricing engine then remains the reference for list price, contract price and the discount rules that the CPQ consumes. We do not revisit the subject here: see our analysis of CPQ and ERP integration.

Governance: Who Can Change a Price, Approval, Margin Floor, Audit Trail

A high-performing pricing engine without governance remains a risk. Four mechanisms to configure from the start of the project:

Change rights. Clearly separate who can view a price, propose a change, validate and activate. The segregation-of-duties principle applies here as elsewhere: the person who negotiates should not be the one who activates the price list alone (see our segregation-of-duties controls before an audit).

Approval workflow. Every price creation or change goes through a flow: request, margin check, management approval, activation on a given date. Dynamics 365’s journal-based approach, where agreements are prepared then validated before posting, illustrates the principle well (Microsoft Learn). Whatever the vendor, an equivalent must exist, native or through workflow.

Margin floor threshold. Define, by family or by customer, a price below which the system blocks or requires higher-level approval. The threshold is based on the ERP’s cost price: its reliability therefore depends on the quality of the standard or average cost. If your costs are questionable, so is the floor. We cover this in our article on gross margin management by product line.

Audit trail. Every price change must keep who, when, old value, new value and reason. For retention obligations, see our article on the ERP audit trail (in French). On the steering side, this trail feeds margin leakage reporting: the gap between list price and net invoiced price, by customer, salesperson, family and channel. This is the indicator that turns governance into action.

Pricing and E-Invoicing: Order, Invoice and Credit Note Consistency

With the spread of e-invoicing, price stops being an internal matter: the invoice is transmitted in a structured format, and discrepancies become visible to the customer in their own system. Three consistency points to check:

  • Order, delivery, invoice: the invoiced price must be the order price, barring a documented revision rule. A gap leads to rejection, dispute or credit note.
  • Discounts on the invoice: line and invoice-level discounts must be transcribed in the right fields of the structured format, with totals that recalculate identically. A different rounding between the pricing engine and the invoice generator is enough to create anomalies.
  • Credit notes and rebates: a year-end rebate or price-correction credit note must reference the original invoice and follow the same calculation logic.

For the French regulatory context, see our guide to 2026 e-invoicing and ERP compliance. The takeaway for your project: test the full circuit (order, invoice, credit note) with your real discount cases before go-live, not just simple invoices.

Implementation in 5 Steps

  1. Map the current state. Inventory every price source: ERP price lists, Excel, contracts, EDI, portal, e-commerce. Measure the number of manually keyed prices on recent orders: this is your baseline indicator.
  2. Set the rules. Write down the resolution hierarchy, discount types, conventions (net price or discount) and retroactivity rules. Have this document signed by sales and finance leadership.
  3. Clean up before migrating. Do not carry over ten years of exceptions. Remove obsolete prices, group customers into segments, and migrate as customer-specific only what is justified. For the general data migration method, see our pre-migration ERP audit.
  4. Configure and test on real cases. Replay a sample of past orders and compare the calculated price with the historical one: every gap is either a configuration error or an exception to regularize.
  5. Steer after go-live. Activate margin leakage reporting, a monthly review of manual prices and the contract expiry alert.

6 Common Mistakes and How to Counter Them

MistakeConsequenceCountermeasure
Migrating all specific prices as-isThousands of unmanageable lines with no ownerSegment customers, keep as specific only what is justified
Undocumented resolution hierarchyDifferent prices depending on channel or personSigned rules document, sandbox test on every channel
Prices with no end dateObsolete conditions applied indefinitelyMandatory end date and expiry alert
Allowing free price entry on ordersManual exceptions returnLocked price, override via workflow with a reason
Margin floor calculated on an unreliable costUnjustified blocks or margin leakageMake the cost price reliable before activating the floor
Ignoring EDI and e-commerce in scopePortal prices differ from order desk pricesInclude every channel in acceptance test sets

Scoping Checklist

B2B pricing scoping checklist for the ERP

  • Is the resolution order (contract, customer, group, standard) written down and approved?
  • Does every price have a start date, an end date and an owner?
  • Net price or discount: is the convention unique?
  • Is the retroactivity of price changes defined in writing?
  • Who can propose, validate and activate a price? Are the roles separated?
  • Is there a margin floor threshold, based on a reliable cost price?
  • Do all channels (order desk, EDI, portal, e-commerce) apply the same engine?
  • Do framework agreements have an expiry alert and an indexation formula?
  • Has the order, invoice, credit note circuit been tested with real discounts?
  • Is margin leakage reporting planned after go-live?

To structure your whole project scoping, download our ERP evaluation grid: 30 criteria scored out of 100 to compare your vendors side by side, including price and discount management.