Deutsch (Deutschland) 
Polski (PL) 
Independent IFS Cloud practice · Sales
The discount that no one approved, on an order that shipped anyway
A sales order line carries a discount, entered as a percentage or an amount off the list price. The discount is a normal selling tool, set on the line at order entry. Whether a line whose discount sits far above what the pricing policy allows can still be confirmed in your setup is worth checking in your own data. Where it can, the goods ship, and the margin the business planned for that part was given away at the keyboard. The discount, the list price and the resulting net sit on every line, so the ones that run past a threshold can be listed.
Key takeaways
- A line discount reduces the net price directly, so a discount above policy is margin the business planned for and then gave away at order entry.
- Where nothing at entry caps the discount, an order can be confirmed at 5 percent or at 50 percent, so a line that runs past the allowed limit goes through.
- This is not the same as a line sold below cost. A discount can stay above cost and still breach the discount policy, so margin leaks without ever tripping a cost floor.
- A pattern of high discounts on the same customer, part or salesperson is a pricing-control signal, because it shows where the policy is being worked around, not just where one order was generous.
- The discount, the list price, the net and the customer all live on the sales order line in IFS Cloud, so a read-only monitor can list the lines above threshold and write nothing back.
1.A line discount changes the net price at entry, and the policy ceiling has to be checked against it
A sales order line discount in IFS Cloud lowers the net selling price from the list or agreement price, entered as a percentage or a fixed amount. It is how a salesperson reflects a negotiated deal, a volume break, or a goodwill gesture on the order. The line stores the list price, the discount and the net that results, so the full picture of what was given away is on the record.
A pricing policy sets a ceiling on how much discount a line should carry without a higher approval. That ceiling can differ by customer, by product group, or by margin band. Whether the order line enforces the ceiling in your setup is worth checking. Where it does not, the line accepts the number a user types, confirms, and moves the order forward.
So the quiet risk is the line that exceeds the ceiling and is confirmed anyway. The customer is happy, the order ships, and the margin erosion shows up only later in a report that no one reads line by line. The record carries the discount and the net it produced, and nobody is comparing them to the policy at the moment it matters.
2.Discounts that break the policy ceiling
A deep discount that follows an approved deal is legitimate. The problem is a discount that breaks the policy ceiling with no approval behind it, or a pattern of them that points at a workaround. The difference is whether the discount exceeds the threshold for that customer or product, and whether the same name keeps appearing, and both are readable on the order lines.
| What you see | What it points to |
|---|---|
| Line discount above the policy ceiling for that customer or product | The core case. Margin the business planned was given away with no higher approval recorded on the order. |
| Same salesperson posting high discounts across repeated orders | A pattern where the ceiling is being worked around routinely, not a single negotiated exception. |
| Same customer receiving above-policy discounts order after order | An account whose real price has drifted below the agreed one, which erodes the margin on every future order too. |
| Discount that leaves the net near or below cost | The most acute exposure, worth reading beside a line sold below cost, because the deal may lose money once freight and handling are counted. |
A line above the ceiling is where the margin goes. The order looks complete and the customer is served, yet the net price sits below what the policy allows for that line. A sales manager reviewing orders one at a time cannot see that a customer has had above-policy discounts on ten orders this quarter. Read the discount against the policy ceiling across the order book, and the outliers stand out.
3.Finding the lines that discounted past the policy
The line discount, the list price, the net price, the customer and the salesperson are all available through standard OData projections, so they can be read without touching a record. Detection compares the discount already on the line against the rules the business sets:
- Discount above the ceiling - lines whose discount exceeds the allowed limit for that customer or product group, so the ones that breached policy surface as a list rather than hiding in confirmed orders.
- Repetition by customer or salesperson - accounts or sellers with high discounts across repeated orders, so a systematic workaround ranks above a one-off negotiated deal.
- Net near the cost floor - lines whose net after discount approaches cost, so a discount that turns the deal unprofitable is caught before it repeats.
Because it is a read-only monitoring pattern, it runs beside sales and writes nothing back to IFS. It adds no object inside the client system, so an R1 or R2 release leaves nothing of ours in your IFS to retest. Before each release I check that the standard projections it reads still match, as part of the subscription. Granting a discount stays a sales decision. The monitor makes sure the above-policy lines are seen while the order can still be reviewed, not a quarter later in a margin report. The same order line data also shows a manual price override, another way margin leaves the business at the point of entry.
4.Rolling it out without noise
- Start with your highest-margin product groups - the parts where a discount hurts the bottom line most are where an above-policy line matters first, so watch those before the whole catalogue.
- Dry-run first - log which lines would have been flagged across a full period before a single alert reaches a sales manager.
- Set the ceiling per customer and product group - a distributor and a direct account carry different agreed discounts, so tune the threshold to the pricing policy rather than one number for all.
- Read only, no footprint - standard OData reads, nothing written back, no new object inside IFS Cloud.
Related reading
5.Frequently asked questions
What is an excessive discount on a sales order line in IFS Cloud?
An excessive discount is a sales order line whose discount, as a percentage or amount off the list price, sits above the ceiling the pricing policy allows for that customer or product group without a higher approval. Where the line is confirmed regardless of the discount size, the order ships and the planned margin is reduced at entry, with the discount and the resulting net price recorded on the line.
How is an excessive discount different from selling below cost?
Selling below cost is a net price that falls under the part cost, a floor breach. An excessive discount is a discount that exceeds the policy ceiling, and it can happen while the net price stays comfortably above cost. A line can breach the discount policy and still be profitable, so a cost-floor check alone will miss it. The two checks answer different questions: one asks whether the deal loses money, the other asks whether it broke the pricing rules.
Why watch discount patterns and not just single orders?
A single deep discount can be a legitimate negotiated deal. A pattern of above-policy discounts on the same customer, part or salesperson shows that the pricing ceiling is being worked around rather than applied. Reading discounts across the order book by customer and seller reveals where the real selling price has drifted below the agreed one, which erodes margin on every future order to that account, not just the one in front of you.
Does this monitoring write anything to IFS Cloud?
No. The line discount, the list price, the net price, the customer and the salesperson are read through standard OData projections and evaluated outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client system. Granting or approving a discount stays a sales decision.
6.About the author
Dariusz Myśliwiec brings 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Know which orders discounted past your policy
Tell me where discount creep hurts your margin most. On a 30-minute fit call we check whether a rule that reads sales order lines against your discount policy by customer and product fits your data. The SCM Automation Pack runs three rules today (unconfirmed purchase orders, late deliveries, stock below minimum), so this would be an additional rule built to order, read-only, with a dry-run period before anything reaches a sales manager.
