Wholesale distribution is a low-margin, high-volume business, so the accuracy of pricing and the discipline of rebate settlement decide whether the model is profitable. A distributor negotiates prices with customers and suppliers, earns and pays volume rebates, and passes through supplier-funded discounts on specific deals. SAP S/4HANA Cloud Public Edition supports this with two connected layers: the condition technique for pricing on every sales and purchasing document, and Condition Contract Management with Settlement Management for the accrual-based agreements that sit on top.
This article explains both layers as they apply to distribution: how prices are determined, how sales and purchasing rebates are modeled and settled, and how the design decisions affect margin visibility. Order-to-cash mechanics, direct-ship fulfillment and returns are covered in the companion articles.
Public Edition prices documents using the condition technique, a rule-based framework in which each element of a price, the base price, discounts, surcharges, freight, and taxes, is a condition type determined from master data and configuration when the document is created. Condition records hold the values (for example a customer-specific net price, a material discount, or a quantity-scaled price), and a pricing procedure defines which condition types apply and in what order.
For a distributor this produces automatic, consistent pricing across large order volumes. Prices can be specific to a customer, a customer and material combination, a price list, or a product hierarchy, and can be scaled by quantity so that larger orders receive better pricing automatically. Because pricing is determined on the document, the same logic applies whether the order was keyed by a user, received by EDI, or created through an API.
| Pricing element | Typical distribution use |
|---|---|
| Base price / price list | Customer- or channel-specific list prices |
| Customer/material price | Negotiated net price for a specific account and product |
| Discounts and surcharges | Volume scales, campaign discounts, small-order surcharges |
| Freight | Delivery charges by weight, value or route |
| Taxes | Country-specific determination integrated with Finance |
Pricing is configured through Self-Service Configuration UIs rather than by modifying code, and where a price must come from an external source, released APIs allow it to be supplied without changing the pricing engine.
Distributors frequently agree terms in advance rather than pricing each order in isolation. Public Edition provides value and quantity sales contracts that hold negotiated conditions and release into individual call-off orders. A quantity contract commits a customer to a volume over a period; a value contract commits a monetary amount. Orders created against the contract inherit its terms and draw down the committed quantity or value, giving both parties a controlled way to honor an annual agreement while still processing day-to-day orders normally.
Above pricing sits the settlement layer, which handles agreements whose value accrues over time and is paid or collected periodically. In Public Edition this is Settlement Management built on Condition Contract Management (CCM). A condition contract stores the terms of an agreement, the business partner, the eligible scope of materials or hierarchies, the rate, and the validity period, and serves as the basis for accruing and settling amounts as business is transacted.
Two directions matter to a distributor:
Because both are built on the same condition-contract foundation, a distributor manages inbound and outbound rebate agreements with one consistent mechanism, and the accruals keep margin realistic between settlements rather than distorting it until a rebate is paid or collected.
The value of the accrual-and-settlement model is that it keeps reported margin honest. Without accruals, a rebate that will eventually be paid to a customer, or collected from a supplier, would not be reflected until settlement, overstating or understating margin in the meantime. Condition contracts post accruals as qualifying business occurs, so the expected rebate is visible on the books continuously. Settlement then converts the accrued amounts into actual credit or debit documents and clears the accruals.
For distributors this supports two things at once: accurate periodic financials, and the operational ability to answer "what is this customer's real net price after rebate?", which is the number that determines whether an account or a product line is worth serving.
A pattern specific to distribution is supplier-funded pricing on individual deals. A supplier agrees that the distributor may sell a product to a particular end customer at a reduced price, and the supplier reimburses the difference, the distributor "charges back" the delta. These ship-and-debit and chargeback arrangements are modeled on the same Condition Contract and Settlement Management foundation as rebates: the eligible customer, product and special price are held in a condition contract, and the recoverable amount from the supplier is accrued and settled periodically.
Because these arrangements can involve high volumes of individual claim lines, modeling them as structured condition contracts rather than as manual credits is what makes them auditable and reconcilable at scale. The exact configuration depends on the agreement pattern and should be validated against current scope.
Distribution pricing often includes free-goods promotions, "buy ten, get one free" or a bonus quantity on a qualifying order. Public Edition supports free goods as a standard pricing outcome, adding the bonus item automatically when the qualifying condition is met, either as extra quantity of the ordered material (inclusive) or as a separate free item (exclusive). This keeps promotional terms inside the automated pricing flow rather than requiring manual line additions.
The design work in this area is to structure conditions and contracts so that they are both accurate and maintainable at scale. The main decisions are:
| Decision | Options | Consideration |
|---|---|---|
| Price differentiation | Customer, customer/material, price list, hierarchy | Balance precision against master-data volume |
| Quantity scaling | Scaled condition records | Reward volume without manual intervention |
| Rebate scope | Material, material group, hierarchy | Granularity vs. number of contracts to maintain |
| Accrual strategy | Per condition contract | Keeps margin realistic between settlements |
| Supplier-funded deals | Condition contracts for chargeback/ship-and-debit | Auditability of high-volume claim lines |
A fit-to-standard assessment should confirm which pricing and rebate patterns are covered by standard scope, model them with condition types and condition contracts, and reserve extensibility for genuinely non-standard calculations. Testing should verify not only that prices and accruals are correct on individual documents, but that periodic settlement produces the right credits, debits and financial postings and clears the accruals cleanly.