Applications
Applications for IFS Cloud, built and maintained by one consultant, not a sales layer.
Each one reads IFS Cloud over standard OData, on a read-only account. None installs an object, a workflow, or a customization in your system, so none has anything to break at the next R1/R2 release.
On this page:
SCM Automation Pack - the ongoing service that monitors purchasing and inventory exceptions. It alerts a named owner before an exception turns into a late delivery or a stockout.
SCM Exception Scan - a one-off, five-day look at the same data, at a fixed price. See what is already sitting in your IFS Cloud before you commit to anything ongoing.
IFS Cloud data distribution - reports and portals for people without an IFS license: customers, suppliers, managers waiting on one number a week.
Pick the application that matches the problem you have today, not the one someone else would have.
IFS Cloud · Purchasing & Inventory exception monitoring
See your exceptions first, or put them under control today?
SCM Exception Scan and SCM Automation Pack read the same purchasing and inventory exceptions in your IFS Cloud data, over the same read-only OData connection. One is a five-day look at your own data, priced once. The other is the ongoing service that keeps acting on what that look would find, every day. This page lines them up side by side so you can pick the one that matches where you are right now.
Key takeaways
- Both services read your IFS Cloud over OData with a read-only account; neither installs anything in it.
- The Scan is a five-business-day, €900 fixed-price look at your own exceptions, ending in a report and a 30-minute walkthrough.
- The Pack is the ongoing service: three Wave 1 rules, maintenance, verification before every IFS release and a quarterly value report, from €1,800 implementation plus €350 or €590 a month.
- Move from the Scan to the Pack within 90 days and the €900 fee is credited in full against the €1,800 implementation. It does not stack with the first-client referral discount.
- Don’t continue after the Scan, and the container is simply removed. Nothing stays behind.
1.The one-sentence version
The SCM Exception Scan is the same observation week that opens the SCM Automation Pack, sold on its own. It doesn’t need any new code: the Scan runs the identical engine in dry-run mode, on a read-only account, so what you see in the Scan report is exactly what the Pack would be watching every day if you kept it switched on.
2.Compare them side by side
| SCM Exception Scan | SCM Automation Pack | |
|---|---|---|
| What it is | A one-off, five-business-day scan of your purchasing and inventory exceptions. Read-only, observation mode only: nothing is sent to anyone. | An ongoing service: three Wave 1 rules running against your live IFS Cloud data, maintained and verified before every IFS release. |
| Price | €900, fixed, one-off. | €1,800 implementation once, then €350/mo (Core) or €590/mo (Plus). |
| What you get at the end | An exception report plus a 30-minute walkthrough with your team. | A quarterly value report, one deduplicated morning digest per owner, and tuning on request under Plus. |
| If you don’t go further | Your integration account is revoked and the container is removed, following the documented decommissioning procedure. Nothing stays behind. | Not applicable. This is already the ongoing service. |
| If you do go further | The €900 fee is credited in full against the €1,800 implementation, within 90 days. It does not stack with the first-client referral discount. | This is the entry point itself. Further rules beyond the three are built on request (€450 each) or included, up to eight, under Plus. |
| When to pick which | You want to see your own data before committing to anything ongoing, with zero further obligation. | You already know you want ongoing coverage and want the observation week, the rules and the reporting running now. |
3.Which one should you start with
Start with the €900 scan
Five business days, read-only, zero commitment beyond the fee itself. You get a report of what’s already sitting in your own IFS Cloud data before you decide on anything ongoing.
Go straight to the Automation Pack
If you already know you want daily coverage, three rules, checks before every IFS release and a quarterly report, skip the standalone scan and start the observation week as part of implementation.
4.Frequently asked questions
Can I start with the Scan and not buy the Pack?
Yes. The Scan is a complete, five-business-day engagement on its own: read-only, observation mode, ending in a report and a 30-minute walkthrough. If you decide not to continue, your integration account is revoked and the container is removed following the documented decommissioning procedure. Nothing stays behind in your IFS or in your infrastructure.
Does the Scan fee really apply against the Pack?
Yes, in full. If you move to the SCM Automation Pack within 90 days of the Scan, the €900 fee is credited against the €1,800 implementation charge, so the Scan effectively costs nothing extra if you continue.
Can I combine the Scan credit with the first-client referral discount?
No. The two concessions do not stack: you pick either the Scan fee credited against implementation or the referral discount on implementation, never both. This keeps the reason the implementation fee exists in the first place, an implementation at €0 would stop separating a client who is genuinely piloting from one who just wants to try for free.
Which one should I start with?
Start with the Scan if you haven’t seen your own exceptions yet and want zero ongoing obligation while you decide. Start directly with the Pack if you already know you want ongoing monitoring and want the observation week, the rules and the quarterly reporting running as soon as possible.
5.About the author
25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Hands-on across IFS Cloud integration (OData, read-only) and the full SCM chain: Purchasing, Requisitions, Inventory, Sales, Invoicing. You talk to the consultant who builds both of these services, 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.
See your own exceptions, or start monitoring today
Read the table above once more, then pick the path that matches where you are. Both start on read-only access, and both start with a conversation about your own data, not a generic pitch.
IFS Cloud · Purchasing & Inventory exception monitoring
SCM Automation Pack
A monitoring service that watches your purchasing and inventory exceptions in IFS Cloud and alerts the named owner before they become a late delivery, a stock-out or a margin leak. It runs as a container in your own infrastructure, reads IFS over OData with a read-only account, installs nothing in it, and never floods anyone with email.
- Three rules ready today: unconfirmed POs, past-due deliveries, stock below minimum
- Read-only OData access: zero objects created in your IFS
- Observation week first: nobody receives a message until you approve the list in writing
- One morning list per owner, deduplicated, never the same alert twice
1.The problem it solves
Automation is possible in IFS, but nobody has time to design it. So the controls that matter live in spreadsheets and inboxes: someone remembers to chase the unconfirmed PO, someone notices the delivery date slipped, someone spots that stock dipped below minimum. Until they don’t.
Manual policing
A buyer’s day disappears into checking states that a service could watch every morning, and the one they miss is the one that hurts.
Silent exceptions
A supplier who never confirmed, a delivery date that quietly passed, a stock level under its minimum: none of these raise an event. They stay invisible until they land as a stopped line or an urgent freight bill.
Fear of customisation
The usual fix breaks at the next release. This service installs nothing in your IFS, so “the system watches it for me” has nothing to break.
2.Three rules ready today, more on request
- SC-01 Purchase order without supplier confirmation - released for N days, no confirmation: supplier reminder plus buyer alert
- SC-02 Delivery date passed, nothing received - buyer alert with the order lines that are late
- SC-03 Stock below minimum - replenishment alert to the named owner
Each rule comes with a one-page card written for the buyer, not the developer: what it checks, who receives it, what to do with it, how to switch it off. Thresholds, recipients and the quiet window are yours to change in the panel without calling me.
Need a rule that is not on the list? A further rule is built on request (€450: design, build, documentation and a volume test on your data) or within the Plus subscription, up to 8 rules. New rules are built by me rather than by you for one reason: a rule that skips the volume test can send hundreds of emails in a single morning, and that is the one failure after which nobody reads alerts again.
3.How it works, day by day
- Day 1: read-only account. Your IFS administrator creates an integration account with read access to a few projections. Fifteen minutes, one-page instruction. Nothing is created in IFS.
- Days 2–3: 60-minute workshop. With your purchasing lead we define what “confirmed order” means in your data, on ten real orders rather than in theory, and agree thresholds and a named owner per rule.
- Days 4–10: observation. The service runs, nobody receives a message. Each day we look at the list together and ask one question per line: would you have wanted this alert? Every “no” becomes tuning.
- Day 11: written sign-off. You approve the list. Notifications go live, first to your own people only.
- Day 14: supplier reminders. After three quiet days of internal alerts, reminders to suppliers are switched on.
- Month 2 onwards. Buyers get one morning list of orders that need a reaction. You get a value report: how many alerts, how many ended in action, which rules nobody touched.
For the first week nobody receives a single message. You see exactly what the service would have sent and decide yourself which of it you want to receive.
4.Pricing
| Implementation (once) | Core | Plus | |
|---|---|---|---|
| Rules | 3 Wave 1 rules | 3 Wave 1 rules | Up to 8 rules |
| Binding to your IFS, 60-min workshop, observation week, tuning, handover, documentation | Included | Via implementation | Via implementation |
| Thresholds, recipients and quiet window changed by you (panel) | Included | Included | Included |
| Verification before every IFS release | Not included | Included | Included |
| Quarterly value report | Not included | Included | Included |
| Tuning on request, additional company or site | Not included | Not included | Included |
| Price | €1,800 once | €350/mo | €590/mo |
Implementation is paid once; then you choose Core or Plus. A further rule on request is €450. One missed delivery date in production costs more than the whole implementation. You are buying the events that don’t happen, not the configuration.
Not sure yet? The SCM Exception Scan (€900, five business days, read-only) shows the exceptions in your own data first, and the fee is credited in full against implementation within 90 days.
5.Why it stays update-safe
Nothing is installed in your IFS. The service reads a few projections over a standard OData connection with a read-only account, so there is no object, no workflow and no modification for the next R1/R2 release to break. Before each IFS release I verify that the projections the rules read still match. Decommissioning is revoking that account and stopping the container.
Three safeguards are built into every rule and are not negotiable: an observation mode that logs instead of sending until you sign the list off, deduplication so nobody gets the same alert twice, and a quiet window so a misconfiguration can never turn into an alert storm. The observation week is written into the contract.
6.What you see after a quarter
After a quarter I show you how many alerts ended in action, and I propose switching off the rules nobody reacted to.
Every purchasing manager has lived through a tool that everyone ignored after three months. This service measures itself against that: a rule with no reaction for 60 days is proposed for switch-off by me, without you having to ask. You pay for alerts that change what a buyer does that morning, not for a dashboard.
7.Why me
25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Hands-on across IFS Cloud integration (OData, read-only) and the full SCM chain: Purchasing, Requisitions, Inventory, Sales, Invoicing. 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.
Independent practice. IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
8.FAQ
Will this break at the next IFS upgrade?
No. Nothing is installed in your IFS: the service reads a few projections over OData with a read-only account. There is no object, workflow or modification for the next upgrade to break, and before each IFS release I verify that the projections the rules read still match.
Won’t automated alerts flood our inboxes?
The first week is observation only: nobody receives a message until you sign the list off in writing. After that, each owner gets one morning digest, alerts are deduplicated so nobody sees the same one twice, and a quiet window stops a misconfiguration from becoming a storm.
What do we need to provide?
Four things: an IFS Cloud integration account with read-only access to the relevant projections; a place to run one container (a small VM or Docker host); HTTPS network access from that machine to IFS; and an SMTP account or a webhook for notifications. Nothing on that list requires a change in IFS.
Can we change thresholds and recipients ourselves?
Yes. Thresholds, recipients, the quiet window and exclusions are your configuration and you change them in the panel without me. New rules are built by me, because each one needs a volume test on your data before it is allowed to send anything.
Can we add rules beyond the three?
Yes. A further rule is €450 on request (design, build, documentation, volume test) or included within Plus, which covers up to 8 rules. The scope stays within SCM: purchasing, inventory, sales and invoicing.
Does the service write anything to IFS?
No. It reads and notifies. The integration account has read access only, and the rules run on a daily cycle rather than reacting to live events, which is the right rhythm for exceptions defined by something that did not happen for days.
What happens when we stop?
Your administrator revokes the integration account and you stop the container. That is the whole procedure, and it is part of the documentation you receive. Nothing remains in IFS because nothing was ever put there.
See it on your data
Book a 30-minute fit call. Tell me where your buyers lose time today, and I’ll show you what the three rules would flag in your own IFS, with a fixed price and an observation week before anyone receives an email.
IFS Cloud · Purchasing & Inventory
SCM Exception Scan
A five-day, read-only scan that shows the exceptions already sitting in your own IFS Cloud data: unconfirmed purchase orders, past-due deliveries, stock below minimum. No emails leave the system, and nothing is installed in IFS. You see what to watch before you pay for a full implementation.
- Five business days, read-only over standard OData
- A short report: the exceptions found, ranked by how actionable they are
- Observation mode: zero notifications, zero trace in IFS
- Fee credited in full against the SCM Automation Pack within 90 days
1.What it does for you
Your IFS Cloud already holds every one of these records, correct and current. The scan reads them the same way the monitoring service does, but only to show you the list, never to send anything.
- Purchase orders in Released with no supplier confirmation after N days
- Delivery dates passed with no receipt posted
- Stock below its minimum
The output is a decision list, not a data dump: the exceptions found, how many are actionable, and which of them you would want to monitor automatically. It is the same week of observation the SCM Automation Pack begins with, offered on its own so you can see your own data first.
2.What you get
- Read-only scan of your live data, in observation mode, with zero notifications
- A short report: the exceptions found, ranked by how actionable they are
- A watch list: which of these you would want to monitor automatically
- A 30-minute walkthrough of the findings with your team
Not included: implementation, ongoing monitoring, process redesign. Those are the SCM Automation Pack, and they are the natural next step.
3.How it works
- Scoping call (30 min). We confirm your modules, IFS version and the pain worth solving first.
- Read-only account. Your administrator creates an OData integration account with read access only. Fifteen minutes of work.
- Observation week (5 business days). The rules run in dry-run. Zero emails leave the system.
- Handover. A short report plus a 30-minute walkthrough. You decide what to keep.
4.Pricing
| Item | Scope | Price |
|---|---|---|
| Exception Scan | Read-only scan, report and 30-minute walkthrough | €900 |
Fixed price. The fee is credited in full against the SCM Automation Pack implementation (€1,800) within 90 days, so the scan costs you nothing if you go on to automate.
5.Risk reversal
The worst case: if the scan finds nothing worth acting on, the report says so in writing, and you keep it as evidence that your exceptions are under control. You have spent €900 to retire a question that was otherwise sitting unanswered.
6.Frequently asked questions
Do you need write access to our IFS?
No. The scan uses a read-only OData integration account and standard projections. Nothing is installed in IFS, nothing is written back, and there is nothing to uninstall when the scan finishes.
Will the scan send anything to suppliers or buyers?
No. The scan runs entirely in observation mode. Zero notifications leave the system. You read the list and decide what you want to be told about, long before anyone is emailed.
What do I need to provide?
Three things. A read-only IFS Cloud integration account with access to the relevant SCM projections; your administrator creates it in about fifteen minutes. A place to run the scan container inside your own infrastructure: a small VM or a Docker host. And network reach from that container to IFS over HTTPS. The scan runs in your network, not on our servers.
How does the scan relate to the SCM Automation Pack?
The scan is the same week of observation the Pack begins with, offered on its own. The fee is credited in full against the Pack implementation within 90 days, so choosing to automate afterwards costs you nothing extra.
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.
See your own exceptions before you pay for anything
Book a 30-minute fit call. You will see which exceptions are sitting in your own data, which three to watch first, and a fixed price for the scan.