Independent IFS Cloud practice · Sales
The price that expires while orders keep asking for it
A customer price list or agreement is not permanent. It has a date it stops being valid. That date is set once, months ahead, and then everyone forgets it, because the price keeps working right up until it does not. On the day after, new order lines no longer price from it. They fall back to a base price, to another list, or to nothing you expected. Sales keeps quoting the old terms. The system quietly stops honouring them. Nobody set out to change a price, and yet the price changed.
Key takeaways
- A sales price list or customer agreement carries a valid-to date. Once it passes, new lines stop pricing from it, and the change happens on its own.
- Nothing warns you the date is coming. The agreement works perfectly until it expires, so there is no symptom until an order is already mispriced.
- This is not a line with no price, where nothing prices at all. Here a price applies, just not the one anyone agreed.
- It is also not an off-agreement price on a live agreement. This is the agreement itself running out of validity.
- Validity dates on price lists and agreements are readable through standard OData, so a read-only monitor can list every one that expires soon, before the orders it prices go wrong.
1.A validity date is a switch nobody watches
Pricing in IFS Cloud is not a single number on a part. It is a set of price lists and customer agreements, each valid for a period, each with a date it starts and a date it ends. The valid-to date is a switch. On one side of it, an order line prices from the agreement. On the other side, that agreement no longer applies and the line prices from whatever is next in the order of precedence.
The trouble is that the switch flips by the calendar, not by an action anyone takes. There is no click, no approval, no message. The agreement that was correct on Friday is simply not selected on Monday, and the order picks a different price without comment. The record still exists. It has just aged out of the window where it counts.
That makes it different from the pricing failures you already watch. A line with no price is loud, because the order cannot proceed cleanly. An expired agreement is quiet, because the order prices fine, at a number nobody chose. It can even slip a line below cost if the fallback price is lower than the deal you meant to honour.
2.How the expiry catches you out
No one plans to let an agreement lapse mid-relationship. It happens at the seams of ordinary account management, in three recurring ways.
| Origin | What happens | Why it survives |
|---|---|---|
| Renewal not done in time | The agreement reaches its valid-to date before the new one is entered | The old terms worked yesterday, so nobody notices the gap until an order prices differently |
| Short-dated promotion | A temporary price is set to expire on purpose, and the follow-up plan never lands | The expiry was intended, but the decision about what replaces it was not made |
| Overlapping lists | Several price lists apply, and the one that expires was the one actually being used | Another list still prices the line, so the order looks priced and the drop goes unseen |
In each case the order still prices, which is exactly why the problem is invisible. The gap surfaces later as a margin that came in wrong, a customer disputing an invoice against the terms they were promised, or a sales manager asking why an account is suddenly on list price. By then the orders are placed and the credits are the cleanup.
3.Detecting the expiry before it prices an order
Price list and agreement validity dates are available through standard OData projections, readable without touching a record. Detection is a matter of looking forward at the dates rather than backward at the damage:
- Agreements and lists expiring within a chosen window - anything whose valid-to date falls in the next few weeks, so a renewal can happen before the switch flips.
- Expired agreements with recent order activity - a lapsed agreement on an account that is still ordering is the one most likely to be quietly mispricing right now.
- Customers who lost their only agreement - accounts that were priced from an agreement and now have none in force, so their lines fall to base or list price unnoticed.
Because this is a read-only monitoring pattern, it runs beside sales and writes nothing back to IFS. It does not extend the agreement, change a date, or reprice an order, and it should not: what a price should be is a commercial decision. It hands the account owner the list of agreements about to lapse, so the renewal is a scheduled task instead of an apology after the fact.
4.Rolling it out without noise
- Look ahead, not behind - a warning weeks before the valid-to date is worth more than a report of orders already mispriced, so lead with what is about to expire.
- Dry-run the calendar - see every agreement expiring this quarter before any of them do, so renewals are planned, not scrambled.
- Rank by active accounts - an expiring agreement on a customer who orders weekly matters more than one on a dormant account, so sort by recent activity.
- Read-only by design - standard OData reads only, nothing extended or repriced back in IFS and no new object installed in the client system.
5.Frequently asked questions
If the order still gets a price, what is the problem?
The problem is that the price is no longer the one that was agreed. When an agreement expires, the line prices from the next source in precedence, which might be a base price, another list, or list price. The order looks priced and moves ahead, but the number can be higher or lower than the deal the customer expects, which shows up later as a margin miss or a dispute.
How is this different from an order priced off the agreement?
An off-agreement price is a line that did not use the agreement it should have, while the agreement is still valid. This is one step earlier: the agreement itself has passed its valid-to date, so it is no longer available to any line. One is a line that missed a live agreement; this is an agreement that is no longer live.
Should the monitor extend or renew the agreement automatically?
No. What a price should be, and for how long, is a commercial decision that belongs with the account owner. The monitor reads validity dates through OData and lists what is about to expire or has already lapsed, then leaves the renewal to a person. Nothing is written back to IFS.
Can it tell which expiries actually matter?
Yes, by pairing the expiry with recent order activity. An agreement lapsing on a customer who orders every week is urgent, while one on a dormant account can wait. Ranking expiries by how active the account is keeps the list short and focused on the agreements that are about to misprice real orders.
6.About the author
Dariusz Myśliwiec brings 25+ years in ERP and supply chain, 17+ of them 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.
See which agreements expire next
Tell me how your team manages customer price lists and agreements. On a 30-minute fit call I’ll show you how the SCM Automation Pack lists every agreement expiring in your chosen window, ranked by which accounts are still ordering, with a dry-run week so the renewals are planned before an order prices from the wrong source.
