Discount policies are the rules that decide how much discount a customer gets on a product — automatically, every time you add a line to a quote, order, invoice, or point-of-sale sale. Instead of typing a percentage by hand on each document (and hoping everyone remembers the agreed deal), you set the rules once and NexerIQ applies the best one for you. This guide walks you through everything on the Discount Policies tab: how discounts are chosen, how to build a policy, how to scope it to the right customers and products, how quantity tiers work, and how to test it before it goes live.

Where to find it

Open the Pricing area (at /platform/pricing/discounts). The page has three tabs — Discount Policies, Price Policies, and Mix & Match Rules. This guide is about the first one, Discount Policies. You'll need the Pricing permission to view it, and permission to write to create or change policies.

How a discount is decided

When a product is added to a sale, NexerIQ gathers every discount the customer could qualify for and applies the single best (highest) one — discounts don't stack on top of each other. The candidates it considers are:

• The customer's own default discount, if they have one on their customer record.
• A flat discount from any customer group the customer belongs to.
• Any discount policy (the rules you create here) that matches the customer, product, date, and quantity — including its base discount plus any quantity tiers.

A few important guardrails:

• If a product is set to not allow discounts, it always resolves to 0% — no policy can override that.
• Every product can have a maximum discount. If the winning discount is higher than the cap, it's reduced to the cap (you'll see this flagged as Capped when testing).
• Discounts are not applied on top of a contracted price (a matching price policy). A contracted price already is the deal.

Creating a discount policy

Click New Discount Policy. A policy is built across three tabs — General, Scope, and Quantity Tiers. You fill in the General tab first and save; Scope and Tiers unlock once the policy exists.

1. General

• Name (required) — a clear label you'll recognise, e.g. "Summer sale 10%" or "Trade customers".
• Active — tick Enable policy to make it live. Inactive policies are never applied.
• Base Discount % — the always-on discount this policy gives (0–100). Leave it at 0 if the discount should come purely from quantity tiers.
• Description — optional notes for your team.
• Codes (Discount Codes section) — optional. Leave empty and the policy applies on its own. If you add one or more codes (type a code and press Enter, e.g. SUMME2026), the discount only applies when that code is entered at the point of sale. Codes are stored in uppercase.
• Validity Window — control when the policy applies:
  • Valid From / Valid To — the date range. Leave Valid To empty for "no end date".
  • Time From / Time To (HH:mm) — an optional time-of-day window, e.g. 08:00–17:00. Overnight windows (e.g. 22:00–06:00) are supported.
  • Applicable Days — tick the days of the week it runs on. Leave all unticked to mean "any day".

Click Create Policy to save. (When editing later, this button reads Save Changes.)

2. Scope — who and what it applies to

The Scope tab decides which customers and products the policy targets. The golden rule: leave a field empty to match everything. A brand-new policy with empty scope applies to every customer and every product.

Customer Scope — narrow by any combination of:

• Customers — specific customers.
• Customer Groups — e.g. "Wholesale", "VIP".
• Customer Categories — your customer category tags.
• Attribute Conditions — fine-grained rules on customer attributes (for example "Region equals North"). Add as many as you like; all conditions must match (AND).

Product Scope — the same pattern for products:

• Products, Product Groups, and Product Categories.
• Attribute Conditions — rules on product attributes; all must match.

Within a list (e.g. three customer groups) any one match qualifies; attribute conditions are then required on top. Click Save Scope when done.

Attribute conditions offer operators suited to the attribute type — Equals / Not Equals / Contains for text, the comparisons = ≠ > < ≥ ≤ for numbers, On / After / Before (and so on) for dates, Is / Is Not for yes/no and single-select, and Includes / Does Not Include for multi-select.

3. Quantity Tiers — bigger orders, bigger discount

Tiers reward larger quantities. Each tier is a Min Quantity and a Discount %. The key thing to understand is that tiers are additive: every tier whose minimum quantity is met is summed, on top of the base discount.

To add one, go to Add Tier, set Min Quantity and Discount %, and click Add Tier. Existing tiers are listed (sorted by minimum quantity) and can be removed with the trash button.

Worked example. A policy with Base Discount % = 5 and two tiers — Min Quantity 1 → 3%, Min Quantity 10 → 2% — gives:

• Quantity 1–9 → 5% + 3% = 8%
• Quantity 10+ → 5% + 3% + 2% = 10%

Activating, editing, and removing

The list view shows each policy's name, validity dates, tier count, status, and last-modified time. Open a policy by clicking its name to edit any tab. Use the Active toggle (on the General tab) to turn a policy on or off without deleting it, and the row tools to delete one you no longer need. You can also export the list.

Test it before you trust it

The Test Discount Resolution tool on the Discount Policies tab lets you preview exactly what a customer would get — no real document required. Choose a Product (required), optionally a Customer (leave as "Any customer" to test the anonymous case), a Quantity, and an optional Discount Code, then click Check. You'll see:

• Effective Discount — the final percentage that would apply.
• Winning Source — what won: the customer's default, a customer group, or a specific discount policy.
• Cap and a Capped badge — shown when the product's maximum discount reduced the result.

This is the fastest way to confirm a new policy fires for the right people, and to debug a discount that isn't behaving as expected.

Tips

• Set Valid From/To on seasonal promotions so they switch on and off by themselves.
• Use the Test Discount Resolution tool with and without a customer, and at different quantities, to verify tiers before going live.
• Remember discounts never stack — if a customer qualifies for several, only the single best applies. Combine effects within one policy using the base discount plus tiers, rather than creating many overlapping policies.
• Need to build a bundle (buy these items, get a combined product) rather than reduce a price? That's a different tool — see Mix & Match Policies & Rules.