Every discount should come from a rule someone wrote down, with an end date and an owner, not from a salesperson editing a price field.
Where margin actually leaks
Margin rarely disappears in one bad deal. It leaks through small, reasonable-looking decisions: a festive discount that was never switched off, a distributor rate that was given to a retail customer, a free-shipping promise that nobody costed, a price typed by hand on a quotation because the price list was out of date.
The common thread is that the price was decided in someone's head rather than in the system. When that happens, nobody can later answer the basic questions: who approved this price, why, and until when?
Start with clean price lists
A price list is the base price of each item for a group of customers. Most businesses need only a few: a standard selling list, a dealer or distributor list, perhaps an export list in another currency, and a buying list for each important supplier.
Keep them simple:
- One price list per real commercial relationship, not one per customer.
- Every item that can be sold has a price on the standard list. A blank price is an invitation to type one in.
- Prices carry a valid-from date, so you can load next quarter's prices in advance and see exactly when they take effect.
In Sundial, each customer or customer group has a default price list, so a quotation picks the right base price without anyone choosing it.
Use pricing rules for everything else
Discounts, volume breaks and promotions belong in pricing rules, not in price lists and certainly not in manual edits. A pricing rule says: for these items or item groups, for these customers, customer groups or territories, within these dates and above this quantity or amount, apply this discount or this rate.
Written that way, a discount becomes something you can read, review and switch off. Some examples of rules that work well:
- Five percent off a product group for orders above a set quantity, for all dealers, for the current quarter.
- A fixed rate for one key account on its three highest-volume items, valid for the length of the contract.
- Buy ten, get one free on a slow-moving line, limited to one month.
When two rules could both apply, give them explicit priorities rather than relying on whichever was created first. A rule that never expires should be rare and should be reviewed at least once a year.
Put a floor under every price
Rules decide the price; controls decide what happens when someone tries to go below it. Two controls matter most.
First, a margin check. Because the ERP knows each item's valuation rate, a quotation can show the margin at the moment it is written. Set a minimum margin by item group, and route anything below it for approval.
Second, an approval workflow for manual discounts. Salespeople sometimes need room to negotiate. Give them a band, for example up to a set percentage on the line, and require a manager's approval beyond it. The approval is recorded on the document, with the name and the time, so the history is clear when the next order comes in.
Make discounts visible after the sale
A discount policy you cannot measure is a discount policy you cannot improve. Because every sales invoice in Sundial carries the price list rate, the applied rule and the final rate, you can report on the gap between them by customer, salesperson, item group and month.
Look for patterns rather than single deals:
- Customers who always buy at the deepest discount, whatever the volume.
- Promotions that raised volume during the offer and then left sales flat afterwards.
- Item groups where realized price has drifted well below list over several quarters.
These are commercial conversations, not accounting ones, and they are much easier to have with the invoice lines in front of you.
Handle the awkward cases deliberately
Some pricing situations need specific handling:
- Free items and samples. Issue them on the order at zero rate with a reason, so stock moves correctly and the cost lands in the right expense account.
- Price changes on open orders. Decide whether confirmed orders keep the old price. Usually they should; write that down and let the system enforce it.
- Foreign-currency prices. Keep a price list in the customer's currency rather than converting on every quotation, and review it when exchange rates move materially.
- Taxes. Keep tax templates separate from prices, so a change in rate does not require touching every price list.
A short review routine
Once a month, someone in sales and someone in finance should look at three things together: rules that expire in the next month, rules with no end date, and invoices approved below the margin floor. It takes less than an hour and catches most leaks before they become habits.
We are designing Sundial so an AI agent can prepare that review for you: listing expiring rules, flagging unusual discounts and drafting the questions to ask, with people making the decisions. To see pricing rules on sample data, try the demo.





