Understand the working context

Keep the unit of sale and the threshold understandable. A quantity of ten units means something different from ten cases, so the catalogue and price list should use a consistent unit. When several pricing conditions exist, review the resulting quotation rather than relying on a remembered headline rate. Customer-specific terms may also affect the final price. Clear examples help the team understand which conditions were used in a calculation.

Put it into practice

  • Agree the product’s unit of sale.
  • Record the relevant minimum quantity for a price entry.
  • Check the customer’s list and any product-specific agreement.
  • Preview representative quantities before issuing the offer.

A practical example

A product has one unit price for smaller orders and another for orders at a higher quantity. The salesperson tests a quotation at both sides of the threshold and checks the displayed pricing source. A fixed customer agreement may produce a different outcome, so it belongs in the same review.

HOW THIS RELATES TO ATLAS

In the current workspace

Atlas supports minimum-quantity price entries and quotation price previews. The calculated result uses the supported list, date, quantity and customer agreement rules.

Explore the product

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.