How Price Adjustment works

Price Adjustment reads the stored rows selected by your target types and conditions, calculates a proposed new value, and builds a preview. The queued consumer repeats the rules against the job and writes the changes.

Amount

The amount is applied to the stored value:

  • 5 adds five units when the operation represents a nominal increase;
  • 5 represents five percent when the selected operation is percentage-based.

Always read the preview's Old Value, New Value, Old Application Type and New Application Type columns instead of inferring the result from the amount alone.

Application type

You can keep the current type or replace it with:

  • Fixed
  • Surcharge
  • Surcharge %
  • Discount
  • Discount %

Relative types need a meaningful base price. Preview at least one row from every target type because Price Lists, Customer Prices and matrix records may use different base-price settings.

Dates

When the target supports dates, setting both dates can create a dated record rather than overwriting the current one. Use this for a planned price period only after checking the preview for duplicate or overlapping rows.

Conditions

Leaving conditions empty addresses all records matching the selected targets and website. For production work, start with a narrow SKU, customer, group or identifier condition and expand only after the result is understood.