--- title: "Buyer Knowledge Risk in IFS Cloud Procurement" date: 2026-08-26 description: "Your best buyer holds years of supplier judgment in her head. What it costs when she is out, and how to move that judgment into IFS Cloud." author: "Dariusz Mysliwiec" categories: - name: "Blog" url: "https://www.ifs-erp.com/blog.md" --- # Buyer Knowledge Risk in IFS Cloud Procurement Independent IFS Cloud practice · Procurement # Why your best buyer is also your biggest risk **Key takeaways** - A senior buyer who knows every supplier by instinct is not just an asset — the eight years of pattern recognition behind that instinct usually exists nowhere except in her head. - The better she is, the less anyone feels the need to write down what she knows — which makes the risk grow in exact proportion to her skill, not despite it. - A replacement inherits a supplier list and a login in IFS Cloud. They do not inherit which supplier’s silence means trouble and which just means a contact is on holiday. - The fix is not documentation nobody will read later — it is turning her judgment into rules IFS Cloud applies automatically, so the function survives the person. She knows every supplier by name. She can tell you which orders need chasing without opening IFS. She has done this for eight years, and she is the reason nothing falls through the cracks on her desk. She is also the reason everything could. If she won a competitor’s offer tomorrow, her replacement would inherit a supplier list and a login — not the eight years of pattern recognition that made her effective. This is not a story about one buyer being irreplaceable. It is a property of any role where expertise lives in a person instead of a process: the organisation only feels safe because nobody has priced what leaves with her. This article looks at why that concentration builds up unnoticed, what it costs the day it is tested, and how to move the judgment — not just the task — into something IFS Cloud can carry. ## 1.Why does expertise concentrate in one person? Nobody sits down and decides to make the procurement function dependent on a single buyer. It happens one competent decision at a time. A supplier misses a delivery once, she notices the pattern before it repeats, and the organisation quietly starts trusting her judgment over the system’s default rules. Three years later she is not running a documented process with occasional exceptions — she is the process, and the documented version in the training folder describes a simpler world that stopped being true a long time ago. The reason nobody intervenes is the reason it is dangerous: she is good at her job. A struggling buyer gets coached, escalated, and eventually supported by a second pair of eyes. A buyer who never drops a ball gets left alone, because there is nothing visibly wrong to fix. The gap between what she knows and what the organisation has captured about what she knows grows every year she keeps performing — and it is invisible for exactly as long as she stays. ## 2.What does the concentration actually cost? The cost does not show up while she is at her desk. It shows up the day she is not — and by then it is too late to build the thing that would have prevented it. - **A blind handover.** A replacement, or a colleague covering for two weeks, gets a supplier list and open orders in IFS Cloud — not the mental model of which suppliers need a phone call before they miss a date. - **Rediscovered problems.** Issues she was quietly managing by instinct resurface as visible incidents, because the person covering does not know they were ever a risk. - **Negotiating leverage.** An organisation that cannot function without one person has none to spare in a conversation about her workload, her role, or her notice period. - **A slow, expensive re-learning curve.** Whoever eventually replaces her rebuilds the same pattern recognition from scratch, at the same cost in missed deliveries it took her to build it the first time. The measure of a healthy procurement function is not how well it runs when the best buyer is in the room. It is how well it runs on the Tuesday she is not. ## 3.How do you see this happening inside IFS Cloud? The concentration itself does not show up as a red flag anywhere in IFS Cloud — it is the absence of something, not the presence of an error. What you can see are its shadows: a small number of buyer codes attached to a disproportionate share of purchase orders that were escalated, chased or rescued outside the standard workflow; suppliers whose confirmation delays never trigger the same generic threshold rule twice, because the buyer intervenes before it fires; and a training folder or SOP that has not been updated since a point release everyone has forgotten the number of. None of that is visible from a summary dashboard. It becomes visible only when someone asks a specific question: for this buyer’s supplier portfolio, what percentage of exceptions were caught by a system rule versus caught by her noticing first? If the honest answer is “mostly her,” the concentration is already real, whether or not anyone has named it yet. ## 4.Tacit judgment versus a documented system rule The goal is not to replace her judgment — it is to stop the organisation’s exposure being entirely proportional to her presence. |   | Tacit judgment | Documented system rule | | --- | --- | --- | | Where it lives | One person’s memory | IFS Cloud, applied consistently | | Survives absence | No | Yes | | Transfers to a new hire | Only through years of exposure | Immediately, on day one | | Auditable | No trace of why a call was made | Logged rule, logged trigger | | Improves with review | Only if she reflects on it herself | Tunable by anyone with visibility | None of this argues she should stop exercising judgment on the cases that genuinely need it. It argues that the routine ninety percent of what she does by pattern — which supplier is drifting, which order needs a call today — belongs in a rule the system enforces, freeing her judgment for the harder ten percent only she can actually add value to. ## 5.How do you capture it without disrupting her? This only works if it is framed — honestly — as protecting the function, not auditing the person. Done the wrong way, it reads as a performance review. Done the right way, it reads as building her a backup. 1. **Interview the pattern, not the person.** Sit with her over her top twenty suppliers and ask what she watches for on each one — not what the SOP says. 2. **Translate the answers into rules.** “This supplier goes quiet before a problem” becomes a behaviour-change check; “this one always confirms by Thursday” becomes a threshold. 3. **Run in dry-run against her own history.** Compare what the rules would have flagged against what she actually caught — gaps on either side are worth another conversation with her, not a silent fix. 4. **Give her the alerts first.** The rollout should make her faster before it makes anyone else able to cover for her — that is what earns her buy-in. 5. **Extend coverage gradually.** Once the rules hold up under her own scrutiny, they are ready to protect the function when she is not there to catch what they miss. Built this way — standard Custom Events, Workflows and PL/SQL inside the IFS Extensibility Framework — the rules stay update-safe and avoid the upgrade tax, the same discipline behind a [supplier behaviour-change signal](https://www.ifs-erp.com/blog/supplier-behaviour-change-signal-ifs-cloud) or an [unconfirmed-PO escalation](https://www.ifs-erp.com/blog/unconfirmed-purchase-orders-ifs). Clear ownership of who can see and change each rule follows the same logic as [segregation of duties in IFS Cloud](https://www.ifs-erp.com/blog/rbac-segregation-of-duties-ifs-cloud). [Book a 30-min call](https://www.ifs-erp.com/book-a-call) [See SCM Automation Pack](https://www.ifs-erp.com/scm-automation-pack) ## 6.Frequently asked questions Isn’t this just documentation? We already have SOPs. Documentation captures what the process is supposed to be. It rarely captures the exceptions an experienced buyer makes by instinct, and it does not act on its own. The goal here is a rule IFS Cloud enforces automatically, not a page someone has to remember to read. How is this different from the risk of an employee leaving? A departure is one moment you can at least plan a handover around. Concentration risk exists every single day she is simply out sick, on leave, or in back-to-back meetings — long before anyone has thought about a resignation. Will she see this as a threat to her role? Only if it is introduced as one. Framed and sequenced correctly — interview first, give her the resulting alerts first, extend coverage only once she trusts the rules — it reads as removing her busywork, not her judgment. Is this update-safe? Yes. It is built with standard Custom Events, Workflows and PL/SQL inside the IFS Extensibility Framework — no core modification, so there is nothing here for the next R1/R2 release to quietly break. ## 7.About the author **Dariusz Myśliwiec** — 25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally — you talk to the consultant who builds it, not a sales layer. **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. ## Build her a backup before you need one If your best buyer’s judgment is currently your only safety net, a dry-run month will show you exactly which of her instincts can become a system rule today. Fixed price, nothing goes live until she has seen it work. [Book a 30-min call](https://www.ifs-erp.com/book-a-call)