TRANXACT.AI সাহায্য

Pricing procedures: discounts and surcharges stacked on the price

A pricing procedure lists the steps that arrive at a unit price: the list price, then discounts and surcharges found by customer, customer pricing group, item or category, with a procedure for each kind of document.

Every company has the Standard procedure, which is the list-price lookup exactly as before. Nothing changes until you add conditions and assign a procedure to a document type. The screens are under CRM › Customers › Pricing Procedures.

  1. Pricing Access Sequences and Access Sequence Steps: the keys a condition record must carry, most specific first (customer and item, then item, then everything).
  2. Pricing Condition Types: a Price, Discount or Surcharge (a <customer discount>, a <freight surcharge>), calculated as a percent of the running price or an amount per unit, found by an access sequence. PR00 is the list price.
  3. Pricing Condition Records: the <5>% for this customer on this item, the <2>% for the item, the <1>% for everyone. The first access step that finds a record wins. Customer Pricing Groups and Customer Pricing Group Assignments give a group of customers shared conditions.
  4. Pricing Procedures and Pricing Procedure Steps: the steps in order (PR00 first), each Mandatory or Shown but not added to the price.
  5. Pricing Procedure by Document: assign a procedure to Quotation, Sales order, Invoice, Point of sale or — since release 20261025 — Purchase order. Tick Apply on save to let a new line left at its untouched default price take the procedure’s price; otherwise the procedure’s price is only recorded beside the line.

Since release 20261025 a condition type can also be a Charge on the document — freight, insurance, packing and forwarding, inspection or customs duty — worked out per document rather than in the unit price. See Charges on orders: freight, insurance, inspection and duty.

Every quotation and sales order line records what the procedure said, step by step, beside the price the line carries, and whether somebody changed it. The pricing simulator shows the same working. How to reuse: percentages and condition names in angle brackets are examples.