B2B Distribution Pricing: Build Explainable and Auditable Rules

Treat precedence as a core business rule

The hard problem is not calculating ten per cent. It is deciding what wins when a contracted customer orders campaign volume through a specific channel. Without precedence, identical situations produce different prices.

Odoo and Oracle document customer, quantity, period, geography, currency, matrix, and effective-date capabilities. The company must still decide its own precedence policy.

Adopt a reference hierarchy and document exceptions

This Atlas hierarchy is a recommendation, not a universal standard. It protects contractual commitments first; a campaign overrides a contract only when the contract permits it.

Separate price replacement from stackable adjustments

Every rule declares its effect: a fixed price replaces the base, a discount reduces a selected price, and logistics fees may be added. Without this model, configuration order creates unexplained margin loss.

Version periods and decisions

A price rule has a start date, optional end date, status, and author. Detect overlapping periods on the same scope and resolve them before activation.

The order price is a snapshot. Keep calculated price, currency, unit, tax rate, winning rule, and adjustments. Repricing happens only after an explicit order change and creates a new audit event.

Put margin control and approval in the flow

The engine must explain the proposed amount and route results outside policy. Compare net price with the finance-approved reference cost without exposing that cost to the customer.

• Assign a business owner to every rule family.
• Apply dual control to sensitive contracts and exceptions.
• Set approval thresholds by margin, amount, or customer type.
• Require a structured reason for every manual override.
• Log old value, new value, author, approver, and time.
• Reconcile ordered, delivered, invoiced, and collected prices.

Test policy with an expected-results matrix

Sales and finance should define expected cases covering quantity boundaries, date changes, and rule conflicts. Keep them as regression tests before each tariff change.

Choose standard features, configuration, or targeted development

Use standard price lists when company dimensions and approvals fit the product model; extended configuration for deterministic rules needing specific roles or integrations; targeted development when pricing encodes a real advantage that standard software cannot express cleanly.

Decide from policy coherence, change frequency, auditability, order and stock integration, and the cost of maintaining custom logic—not from the number of existing spreadsheets.