Dealer Portal Pricing, Discounts and Credit Limits

Dealer portal pricing involves more than displaying a price list. The applicable list, order of discounts and point at which a price becomes binding must be explicit. Credit control also goes beyond showing an account balance: pending orders may need to reserve part of the customer's available credit.

Assign ownership of pricing rules

If the ERP manages prices, reproducing its logic independently in the portal can create disagreements. Specify the source of each value, acceptable freshness and behaviour when the source is unavailable. Not every implementation requires a live request for every display, but the age of cached information should not be concealed.

DecisionRule to document
Price listDealer, currency, territory and validity dates
DiscountsPriority of contract, promotion and quantity rules
UnitsWhether the price applies to an item, case or another unit
Tax and currencyDisplay basis and values used for the order
ConfirmationWhen the commercial price is fixed

Two discounts do not necessarily add together

Take an illustrative list price of €100. Applying a 10% reduction followed by 5% off the remaining amount produces €85.50. Adding the percentages and applying 15% produces €85. The difference can arise from an undefined business rule rather than a programming defect.

Approve the calculation with a sample order. Is rounding performed per line or on the total? When are tax, delivery and minimum-order conditions applied? What happens to an open basket when a promotion expires? Include these decisions in acceptance criteria rather than leaving them to the interface designer.

Include pending commitments in credit checks

Suppose an illustrative policy starts with a €10,000 limit, subtracts €6,000 outstanding and reserves €2,000 for accepted orders. That leaves €2,000 available. A new €2,500 order should follow the defined approval route rather than being silently accepted. This is an example policy, not financial advice or a universal credit formula.

If two users place orders simultaneously, both must not independently consume the same remaining allowance. Where the ERP or finance system owns final validation, a portal pre-check must not be presented as final approval. If a transfer times out, establish whether the order was created before submitting it again.

Test the exceptions during the pilot

  • Two dealers see only their own applicable prices.
  • A changed basket price is clearly presented for fresh confirmation.
  • An order exceeding the limit reaches the correct approver.
  • Cancellation releases a reservation under the documented rules.
  • Retrying the same submission does not create a second commercial order.

Keep the calculation inputs and decision history available to authorised staff. Otherwise a price dispute becomes a comparison of screenshots rather than an explanation of the rule used.

Must every price be real time? No. Display freshness and final order validation are separate decisions that should reflect the business risk.

Explore our B2B portal development approach. A few representative orders can make pricing and approval requirements much easier to define.

Explore sample order screens in our Dealer Order Platform product concept. The screens and data are fictional.

Discuss your pricing and approval rules

Related guides

Technical references

Sources checked: 10 November 2026. These documents illustrate discount precedence, credit checks and safe retries in specific products; they do not imply identical support in every ERP. Verify the selected API’s rules and the point at which an order is confirmed.