Independent IFS Cloud practice · Implementation
Key takeaways
Most articles about ERP business impact are written from the brochure. This one is written from the projects. I have spent seventeen years inside IFS, from Apps 7.5 through Cloud, and the pattern that repeats is not that companies pick the wrong system. They pick a capable one and then implement it in a way that throws the capability away: a template nobody reuses, an automation layer nobody trusts, reports rebuilt one for one from the old system because nobody had the authority to delete any of them.
So this is not a list of what IFS Cloud can do. It is a walk through the places where a decision taken during implementation determines whether the platform pays for itself or just replaces one kind of manual work with another. Where a topic deserves its own treatment, I have linked to the longer piece on the ifs-erp.com blog rather than compressing it into two sentences here.
Grouping sites so they share parts, defaults and process setup is sold as a speed feature. It is really a consistency feature, and the speed is a side effect. When site four inherits the purchasing parameters that sites one to three already run on, you are not just saving a week of configuration. You are removing the possibility that site four quietly does receiving differently, which is what costs you two years later when someone tries to compare performance across the group and finds the numbers are not measuring the same event.
The catch is that a cluster only helps if the template being cloned is one somebody defended. Rolling out a bad standard quickly is worse than rolling it out slowly, because a slow rollout at least gives each site a chance to object. I ask for the template to be signed off by the person who will own the process across all sites, not by the site that happened to go first. That is also where the multi-site purchasing decisions belong: whether demand consolidates centrally, and how stock moves between sites once it has.
Further reading: centralised purchasing in IFS Cloud, distribution orders between sites, and from planning to go-live.
IFS Cloud gives you three tools that cover most of what people used to write code for, and knowing which one to reach for is the whole skill. A Quick Report reads data out: a saved query for a list or an extract, with no logic. A Custom Field stores something the standard data model does not. A Custom Event reacts when a row changes, and can hand off to a Workflow that routes an approval, sends a notification, or calls out to another system.
The failure mode is predictable. Teams discover Custom Events, like them, and attach one to everything. Six months later there is an event layer nobody can explain, firing on saves that were never meant to be significant, and the business has learned to ignore the notifications it produces. The second failure mode is subtler: reaching for a Custom Event when the requirement is actually a scheduled check. An event fires when a row changes. It cannot fire because a row has not changed, which is exactly what an unconfirmed order or an untouched receipt is.
Where the requirement crosses a system boundary, the answer is usually an interface rather than an in-system automation. IFS Cloud's OData projections are the normal integration surface, and keeping the orchestration outside IFS keeps that logic out of your ERP, where it would otherwise become one more thing to retest at every release.
Further reading: Custom Events explained, Quick Reports vs Custom Fields vs Custom Events, IFS Cloud API integration, orchestrating IFS Cloud with n8n. Work that has already been built once sits in the configurations and interfaces sections of the marketplace.
IFS Cloud ships R1 and R2 every year. That cadence is the biggest single change in how you should think about customisation, and it is where legacy habits do the most damage. On Apps 9 or 10 an upgrade was an event you prepared for over months, so carrying technical debt between them felt survivable. On Cloud it arrives twice a year, and anything built outside the Extensibility Framework has to be checked, and often reworked, on that same rhythm.
The boundary is simple to state and easy to cross by accident. Extending the data model with Custom Fields, adding logic through Custom Events and Workflows, adapting screens through configuration: all inside the contract, all carried forward. Touching a core object, or building a report or an interface directly against an internal view rather than a published projection, puts you outside it. Nothing stops you at the time. The bill arrives at the next release, and at every release after that.
I have watched this go wrong in both directions. Companies that refuse all extension end up with a shadow layer of spreadsheets doing the work the system was not allowed to do, which is worse, because at least a customisation is visible. The honest position is that some extension is necessary, and the only real question is whether it is built where the platform will maintain it for you.
Further reading: update-safe extensions, the true cost of customisation, clean core in an SCM context, the upgrade tax, the upgrade readiness checklist, and what a release actually brings, with 25R2 purchasing as the worked example. Scoped modification work is listed under marketplace modifications.
Ask a buyer what goes wrong and you get something dramatic: a late shipment, a line stopped for a missing part. Look in the data and the costly problems are the undramatic ones, because nothing in the system objects to them.
| What is sitting there | Why nobody sees it | What it turns into |
|---|---|---|
| A released PO the supplier never acknowledged | The order is valid and open. No field says "ignored" | A delivery date everyone planned around that was never agreed |
| Goods received, invoice never matched | Both records are individually correct | An accrual that grows quietly until period end |
| A supplier price that moved between orders | The new price applies cleanly, exactly as configured | Margin erosion found during an annual review |
| A buyer who stopped ordering from a usual source | Every individual order is legitimate | Concentration risk, or a supplier problem nobody escalated |
All of this is detectable, and all of it is readable through standard OData projections on a read-only account. That means a monitor can look for it daily without touching a record, installing an object, or adding anything the next release has to be checked against. It is the design principle behind the SCM Automation Pack, and the reason the five-day exception scan exists as a way to see what is already in your own data before committing to anything ongoing.
On the physical side the same principle applies to warehouse work. Picking strategy and packing proposals are configuration decisions that quietly set your throughput ceiling, and they are rarely revisited after go-live.
Further reading: unconfirmed purchase orders, what unmatched receipts do at period end, supplier price changes, advanced picking strategies, the packing proposal.
Anomaly detection, demand forecasting and predictive maintenance are genuinely useful, and they all rest on the same unglamorous foundation: whether your master data is good enough for a model to learn from. A forecast built on lead times copied out of the legacy system in 2019 and never reviewed will be precise, confident and wrong, and it will be harder to challenge than a human guess because it arrives with a number attached.
The second thing the demo leaves out is what happens to the output. Detection is the easy half. The half that decides whether any of it pays off is routing: who receives the signal, how it reaches them, and what happens when they do nothing. An alert stream with no named owner and no escalation is a mailing list, and people unsubscribe from mailing lists in their heads long before they do it in the client.
That is why I design exception rules around the recipient rather than the condition. One deduplicated digest per owner per day beats forty individual notifications that are each technically correct. And a rule that cannot state in one sentence what the recipient is supposed to do about it does not ship.
Further reading: alert fatigue and exception design, the cost of missed exceptions, detecting supplier behaviour change, the data attention gap, assumed vs confirmed records, read-only OData monitoring.
Crystal Reports layouts from Apps 9 and 10 do not carry across to IFS Cloud. That is the fact that matters for your plan, whatever any vendor's support calendar says, and it is usually discovered later than it should be, because reporting gets treated as a workstream that can start once the real configuration is done.
IFS Cloud splits the job across different tools. Quick Reports handle lists and extracts: saved queries, no layout ambition, self-service for anyone who can be trusted with a data set. Laid-out business documents are produced through IFS Cloud's own report layout tooling. Analysis and dashboards belong in the reporting and analytics layer rather than in a printed report at all. Trying to recreate a 200-item Crystal inventory inside any one of these is how reporting becomes the critical path.
The work that actually saves you time is triage, and it is a business job rather than a technical one. Pull the usage data first. Most report inventories contain a long tail nobody has run in two years, a middle band that exists because one person likes the format, and a small core the business genuinely runs on. Rebuild the core properly, convert the middle band to Quick Reports or a dashboard, retire the tail. The conversation about retiring the tail is the hard part, which is why it needs to start early and needs someone senior to close it.
Further reading: when a Quick Report is the right answer, and the reports section of the marketplace.
Permission sets in IFS Cloud are capable enough to express proper segregation of duties. Whether they end up doing so is decided in the first six weeks of the project, when someone is under time pressure and the fastest way to unblock testing is to grant a broad set to a group and move on. That grant is almost never revisited, because nothing breaks. It surfaces at the first external audit, when a tester asks who can both create a supplier and approve a payment to it, and the honest answer takes a fortnight to assemble.
Design the role model against the process rather than the org chart, and build it while the process design is still fresh in everyone's head. It costs days then and weeks later. The same applies to standards work: if you operate under ISO requirements, the evidence those audits want is largely a by-product of decisions you are already taking, provided you record them as you go instead of reconstructing them afterwards.
Further reading: RBAC and segregation of duties, permission sets in IFS Cloud, ISO standards in IFS Cloud, and the security section of the marketplace. My own view on the wider ownership question sits on the data governance page.
Every implementation plan has a migration workstream, and most are optimistic by the same margin. The reason is consistent: the effort is not in loading the data, it is in deciding what the data should say. Loading is mechanical. Agreeing that these 4,000 part records are the ones worth keeping, that this status code maps to that one, and that a customer with no valid tax ID is a customer you are not going to migrate, is a series of business decisions with no obvious owner.
Two habits change the outcome. Rehearse the load more than once, on a schedule, with a defined cut of source data each time, so the failure list shrinks between rehearsals instead of being discovered on cutover weekend. And treat validation as its own deliverable with its own sign-off rather than as the last step of loading, because IFS Cloud enforces its business rules at load time: well-formed source data can still be rejected for violating application logic nobody had read.
Further reading: the data migration checklist, how FNDMIG and the Data Migration Manager fit together, and the data migration section of the marketplace.
In most of the companies I work with, a large amount of operational knowledge lives in one person's head and one person's spreadsheet. The buyer who knows which supplier actually delivers on time regardless of what the lead time field says. The planner whose workbook reconciles two things the system does not reconcile. None of this shows up in an ERP assessment, and all of it walks out of the building when that person leaves.
An implementation is the one moment when you have a mandate to surface it. Every shadow spreadsheet is a documented requirement waiting to be read: it exists because the system does not do something, and finding out what that something is tells you more about your real process than a workshop will. Some of them should become configuration. Some should become a Quick Report. A few are genuinely someone's judgement and should stay human, but at least then you know where they are.
The same logic applies to the implementation record itself. Decisions taken in month two get questioned in month eleven by people who were not in the room, and a project that cannot answer "why is it set up this way" reopens settled arguments for the rest of its life.
Further reading: shadow spreadsheet risk, knowledge loss when people leave, buyer knowledge concentration, and the implementation documentation kit if you would rather not build the templates from scratch.
I am wary of quoting percentage improvements. Published ranges come from situations you cannot inspect, with baselines nobody defined, and a number borrowed from another company's business case is not evidence about yours. What I can offer is the short list of measures that survive contact with an actual steering committee.
Further reading: ERP ROI analysis, why go-live is a load test, the implementation crisis.
If you are live on IFS Cloud and this article has described your situation rather than your plan, the order that works is roughly this. Find out what is actually in your data before redesigning anything, because the exception population usually contradicts the received wisdom about where the problems are. Then fix the governance decisions that get harder with time: the role model, the report inventory, the ownership of master data. Automation comes after that, not before, because automating a process nobody owns only makes it produce wrong answers faster.
What I do is on the offer page, the platform view is on the IFS Cloud page, and the process side sits under business process optimisation. The applications themselves, including the read-only exception monitoring described in section 4, live on ifs-erp.com.
No, but the work changes shape. Before go-live it is a design decision that costs nothing extra. After go-live it is an inventory exercise: list everything built outside the Extensibility Framework, establish what each item actually does, and decide case by case whether to rebuild it inside the contract, replace it with standard functionality, or accept the maintenance cost knowingly. The last option is legitimate. What is not legitimate is not knowing which category each item falls into, which is the usual starting position.
No. In most projects I see, the unclaimed value sits in exceptions a plain query would find: orders nobody confirmed, receipts nobody invoiced, prices that moved. That is rule-based detection rather than machine learning, and it works on data that is merely adequate. Model-driven forecasting is worth doing once master data has an owner and a maintenance routine, and worth postponing until it does.
Yes, and that is the approach I prefer for anything that only needs to read. Standard OData projections plus an integration account with read permission are enough to detect the exception patterns in section 4. Nothing is installed in IFS, nothing is written back, and there is no object for the next R1 or R2 release to break. If you want to see the output before committing to anything ongoing, the five-day exception scan produces the same report in observation mode only.
Budget the triage, not the rebuild. Pulling usage statistics and getting a decision on what to retire takes longer than rebuilding the reports that survive, because it needs business sign-off rather than developer time. Start it in parallel with configuration rather than after it, and give the retire list an owner with the authority to say no. Teams that skip this step rebuild everything one for one and carry the whole inventory forward, including the part nobody has opened since 2019.
The configuration saving is small at that scale. The consistency saving is not, and it compounds: two sites configured independently will diverge on receiving, costing and reporting definitions within a couple of years, and reconciling them later is considerably more work than agreeing a shared template now. If there is any prospect of a fourth site, an acquisition, or a group-level report, treat it as worth it.
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. Based in Kraków, delivering remotely across Europe and globally through an independent practice.
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.
If you are scoping an IFS Cloud implementation, or you are already live and suspect the value case has quietly gone missing, a short call is the fastest way to work out which two or three of the eleven sections above are actually costing you something.
Supply chain in IFS Cloud · Implementation design
Supply chain management in IFS Cloud is one chain of records, from the customer order through planning and purchasing to the warehouse, then the shipment and the invoice. A wrong setting in one area shows up as an error in the next, which is why SCM projects stall at the hand-offs, not inside a single screen.
IFS Cloud SCM covers sales orders and supply planning, procurement, inventory and warehouse operations, shipping and returns, plus the postings each of them creates. All of it runs on the same parts and suppliers in one system. The decisions that matter most are the ones that connect these areas: how demand reserves stock, how planning creates supply, and how warehouse transactions reach finance.
Key takeaways
Supply chain management in IFS Cloud is made up of seven connected process areas, and each one has a design decision that the next area depends on.
| Area | Main records | Decision that is costly to change later |
|---|---|---|
| Sales and order promising | Customer orders, order types | How the order type drives the flow and how delivery dates are promised |
| Supply planning | Inventory parts, planning parameters, MRP | Which planning method each part uses |
| Procurement | Purchase requisitions, purchase orders, supplier quotations | Sourcing rules and who approves what |
| Inventory and warehouse | Sites, warehouses, locations, reservations, warehouse tasks | Warehouse structure and reservation rules |
| Shipping | Shipments, consolidated shipments, handling units | Shipment types and how much of the process runs automatically |
| Returns and corrections | Return material authorizations, undo delivery | When a correction is an undo and when it is a return |
| Finance link | Inventory transactions, postings | Posting control for each transaction type |
The shipping row shows how tightly the areas are tied. The IFS Cloud documentation Shipment: hints and limitations defines a shipment line as a subset of the quantity of a source line, and states that the shipment type controls how the shipment process is executed. A shipment type chosen without the order and warehouse teams therefore decides their work as well.
Each supply chain area needs a small number of decisions taken by the process owner before the consultant configures anything, because configuration only records those decisions.
SCM projects in IFS Cloud stall where one workstream's setting becomes another workstream's problem, and these hand-offs follow a recognisable pattern.
The common cure is an end-to-end test case per business flow, run by the owners of every area together, from customer order to posting. Features that are configured but not used to the full are listed in five underused IFS Cloud SCM features.
AI functions in IFS Cloud work on the same supply chain records as users do, so they add value only on top of a sound SCM design. The documentation IFS.ai Copilot for Product Areas lists assistants for supplier quotation evaluation and supplier performance evaluation, among others. IFS Cloud 25R2 added Digital Workers such as a Supplier Order Manager and an Inventory Replenisher. What these functions can and cannot do is covered in AI in IFS Cloud.
Exceptions in the chain still need someone to see them in time: released purchase orders the supplier has not confirmed, overdue deliveries with no receipt, and stock below its minimum. For those three exceptions there is a read-only scan on my product site, the SCM Exception Scan.
Designing the chain itself, area by area and with the hand-offs tested, is the scope of my IFS Cloud SCM implementation service.
IFS Cloud SCM includes customer orders and order promising, supply planning and procurement, inventory and warehouse management, shipping and returns, and the link to finance through inventory postings. All these areas work on shared parts and suppliers in one IFS Cloud system.
The supply chain settings in IFS Cloud that are hardest to change after go-live are warehouse structure and reservation rules, followed by lot or serial tracking, the planning method per part and posting control, because live transactions and stock already depend on them. These decisions belong to process owners before configuration.
Supply chain implementations in IFS Cloud stall at the hand-offs between areas: planning parameters that buyers do not trust, reservation rules decided late, corrections without a rule and inventory postings that finance sees only in the last test cycle. End-to-end tests per business flow expose these hand-offs early.
Supply chain processes in IFS Cloud use AI through IFS.ai Copilot assistants, for example for supplier quotation evaluation and supplier performance evaluation, and through IFS Loops Digital Workers introduced in IFS Cloud 25R2, such as the Supplier Order Manager and Inventory Replenisher. They answer and act on the company's own SCM data.
A supply chain implementation in IFS Cloud should start with the business flows from customer order to posting and the decisions each process owner must take, from order types and planning method to sourcing, warehouse structure and posting control. Configuration then records decisions that are already made.
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 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 does the work, not a sales layer.
Selected clients from my IFS work: 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.
Bring one business flow, from customer order to posting. In a technical call we walk it through IFS Cloud and mark the decision that is missing or the setting that breaks the next area.
Book a technical call about your SCM design See IFS Cloud SCM implementation
IFS Cloud AI · IFS.ai Copilot · Digital Workers
IFS Cloud ships AI as named functions inside the ERP: Copilot assistants on specific pages and, from 25R2, Digital Workers for order and replenishment work. Each one answers from your own IFS Cloud data, so its quality is the quality of that data and of your permission design.
IFS Cloud AI is delivered as IFS.ai: a Copilot that answers questions about IFS Cloud and about your own records on supported pages, and, from release 25R2, IFS Loops Digital Workers that handle defined tasks such as customer orders, supplier orders or inventory replenishment. On supported pages Copilot answers from the records in your IFS Cloud, and a user receives insights only from data that the user is authorised to access.
Key takeaways
IFS.ai Copilot is an assistant panel in IFS Cloud that answers general questions from IFS-published documentation and, on supported pages, questions about your own records. The IFS Cloud documentation page IFS.ai Copilot for Product Areas lists the product-specific assistants and states that users will only receive insights from IFS Cloud data to which they have authorized access.
For supply chain work, the assistants listed for 25R2 include:
| Area | Copilot assistant |
|---|---|
| Procurement | Supplier Quotation Evaluation, Request for Quotation Supplier Selection |
| Supplier relationship management | Supplier Performance Evaluation |
| Sales | Sales Quotation |
The supplier quotation assistant shows what this looks like in practice. For the order quotation approval pages, the Supplier Quotation Evaluation documentation lists predefined questions such as “Which suppliers will meet wanted delivery date?”, and the assistant answers from quotation prices and discounts and from supplier ratings already recorded in IFS Cloud. The buyer still approves the quotation. Recent purchasing changes in the same release are covered in new purchasing functionality in IFS Cloud 25R2.
IFS Loops Digital Workers are AI agents introduced with IFS Cloud 25R2 that carry out defined operational tasks across systems instead of only answering questions. The IFS Cloud 25R2 announcement names five initial Digital Workers:
| Digital Worker | Task |
|---|---|
| Customer Order Manager | Order processing and end-to-end order fulfilment |
| Supplier Order Manager | Keeping supplier orders accurate and on time |
| Inventory Replenisher | Monitoring and replenishing inventory to reduce stockouts and overstock |
| Operations Analyst | Consolidated information from multiple sources |
| Material Replenisher | Making critical materials available on time for production or service |
The same announcement describes the decision model as autonomous execution within governed parameters, with a human in the loop for exception management. In a project, “governed parameters” means concrete settings you own: which orders an agent may process alone, which exceptions go to a person, and who that person is.
AI in IFS Cloud depends on your data because the assistants answer from your own records, and on your permission sets because each user gets answers only from data that user may see. A supplier ranking is only as good as the supplier ratings and prices behind it, and an inventory agent only as good as the planning parameters on the part.
Three checks come before enabling any assistant or agent:
A company should introduce AI features in IFS Cloud one process area at a time, starting where the data is already clean and a person reviews every result. Procurement quotation evaluation is a reasonable first area, because the buyer approves each quotation anyway and can compare the assistant's answer with the record.
Preparing the data and the permission sets for these features, with an owner for each process, is part of my services for IFS Cloud.
IFS Cloud provides AI through IFS.ai: the IFS.ai Copilot, with product-specific assistants on pages such as supplier quotation evaluation and supplier performance evaluation, and, from release 25R2, IFS Loops Digital Workers for tasks such as customer order processing or inventory replenishment.
IFS.ai Copilot product-specific assistants on supported IFS Cloud pages answer questions about the company's own records, such as supplier quotations. According to the IFS Cloud documentation, each user receives insights only from IFS Cloud data that the user is authorised to access, so permission sets limit what Copilot shows.
IFS Loops Digital Workers are AI agents announced with IFS Cloud 25R2 that execute defined tasks. The five initial Digital Workers are Customer Order Manager, Supplier Order Manager, Inventory Replenisher, Operations Analyst and Material Replenisher, working within governed parameters with a human in the loop for exceptions.
The IFS.ai Copilot supplier quotation assistant in IFS Cloud answers questions about quotations and supplier ratings, while the buyer approves the quotation. Digital Workers act within parameters the company sets, with exceptions handed to a person, so the company decides how much is automated.
Before enabling AI in IFS Cloud, clean the master data of the process area, review the permission sets of users on the pages where Copilot runs, and name the role that accepts or rejects each suggestion. IFS Cloud AI answers from company data, so data errors become answer errors.
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 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 does the work, not a sales layer.
Selected clients from my IFS work: 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.
Pick the process area where you want AI first. In a technical call we check the master data, the permission sets and the decision owners for that area, and you leave with a list of what to fix before switching anything on.
Book a technical call about AI in IFS Cloud See services for IFS Cloud
IFS Cloud order delivery · Undo Delivery
Undo Delivery reverses a delivery that was registered by mistake. It is the right tool for a booking error, not for goods the customer sends back, and it stops working as soon as an invoice or a return exists.
Undo Delivery in IFS Cloud reverses a registered delivery of a customer order, a shipment or a consolidated shipment, and moves the customer order back to Partially Delivered, Picked or Released. It works only while no invoice and no return material line exist against the delivered line, so an existing invoice has to be cancelled first.
Key takeaways
Undo Delivery reverses the delivery transaction and puts the order back into a state where it can be corrected and delivered again. The IFS Cloud documentation page Undo Delivery lists these effects:
| Object | Effect of Undo Delivery |
|---|---|
| Customer order | Status changes to Partially Delivered, Picked or Released, depending on what remains delivered. |
| Shipment that was closed | Status goes back to Complete, so the shipment can be corrected before it is delivered again. |
| Shipment order | Status stays In Progress. |
| Rental order | Deliveries can be undone regardless of the rental line status, in the normal order flow only. |
The shipment side follows the shipment statuses described in Shipment: hints and limitations: undo returns the shipment to Complete, after which Undo Complete opens it for changes. Consolidated shipments are undone per shipment, as described in consolidated shipment in IFS Cloud.
Undo the delivery when the delivery transaction itself is wrong; create an RMA when the delivery was right and the goods came back. The two leave different records: undo erases the delivery as if it had not happened, while an RMA keeps the delivery and adds a return with its own receipt, inspection and credit.
| Situation | Use | Reason |
|---|---|---|
| Delivery registered for the wrong line or quantity, goods never left | Undo Delivery | The transaction is an error, and the stock is still in the warehouse. |
| Delivery registered with wrong delivery terms, not yet invoiced | Undo Delivery, correct, deliver again | The terms are corrected before anything reaches the invoice. |
| Wrong delivery, already invoiced | Cancel the invoice, then Undo Delivery | The documentation requires the invoice to be cancelled first. |
| Customer sends part of the goods back | RMA | The delivery happened. The return needs its own receipt and credit, and a return line then blocks any undo. |
The return flow is explained in customer returns in IFS Cloud: how the RMA flow works. If a return material line was created by mistake and nothing has been returned or scrapped on it, the documentation allows removing the customer order reference from that line, which lifts the block.
Undoing a customer delivery in IFS Cloud takes four checks and one action, and the checks decide whether the action is allowed at all.
Handling units, internal transfers and package parts are the cases where Undo Delivery is restricted or gives a partial result.
Undo Delivery causes trouble when it is used as a general correction tool by people who do not see its effect on finance and stock.
Who may undo a delivery, and under which conditions, is a design decision for the order-to-cash process. I take it with the process owner as part of an IFS Cloud SCM implementation.
Undo Delivery in IFS Cloud reverses a registered delivery of a customer order, a shipment or a consolidated shipment. The customer order status changes to Partially Delivered, Picked or Released, and a closed shipment goes back to the Complete status so it can be corrected.
A customer delivery in IFS Cloud can be undone after invoicing only if the invoice is cancelled first. The IFS Cloud documentation states that an existing invoice has to be cancelled before Undo Delivery, so the cancellation should be agreed with finance.
A customer return in IFS Cloud goes through a return material authorization (RMA), because the delivery really happened and the return needs its own receipt and credit. Undo Delivery is for a delivery registered in error, and a return material line against the customer order line blocks Undo Delivery.
A shipment delivery in IFS Cloud is undone as a whole, from the shipment header, not line by line. For deliveries made from a customer order, single lines can be undone until a delivery note is created; after that, only the total delivery for that delivery note can be undone.
Undo Delivery for a transfer inside one company in IFS Cloud works only while the delivered part and its handling unit are still in transit. When the receiving site or remote warehouse has already received the parts, the delivery can no longer be undone and the correction needs a new movement instead.
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 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 does the work, not a sales layer.
Selected clients from my IFS work: 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.
If undo, returns and invoice cancellations depend on who handles the case, the order-to-cash design has a gap. In a technical call we go through your correction cases and decide who does what in IFS Cloud.
Book a technical call about your delivery process See IFS Cloud SCM implementation
IFS Cloud reporting · Crystal Reports deprecation
The Crystal Reports integration in IFS Cloud is deprecated and IFS plans to remove it in 26R2. Each kind of Crystal report has a different replacement, so the first job is to sort your reports by type, not to start rebuilding.
IFS has deprecated the Crystal Reports integration in IFS Cloud and, according to an IFS employee in the IFS Community, plans to remove it in 26R2. Operational report layouts move to IFS Report Studio, ad-hoc Crystal Quick Reports move to Lobbies or Power BI, and a customer who wants to keep Crystal after the removal needs a custom integration.
Key takeaways
The Crystal Reports integration in IFS Cloud renders report layouts designed in Crystal against data that IFS Cloud prepares. In practice it touches three kinds of objects, and each one leaves the integration by a different route:
This article sorts those objects by replacement. The release-by-release status is kept short in Crystal Reports in IFS Cloud, and the full rebuild method (inventory, triage, rebuild patterns, testing) is in IFS Cloud Crystal Reports: release status and migration.
The Crystal deprecation plan in IFS Cloud has had three versions, and a project plan built on the first or second version is now wrong. All three are visible in the public IFS Community thread Removal of Crystal Reports in 25R1.
| Version of the plan | What it said | Where it was published |
|---|---|---|
| First notice | The integration was planned to be removed entirely with 25R1. | Deprecation log entry quoted in the first post of the thread, January 2025 |
| Revised notice (20 February 2025) | 24R2: deprecated, still available, fully functional and supported. 25R1: no longer sold, still supported for 24 months for upgrading customers with existing Crystal licences. 25R2: current integration no longer available. | IFS Cloud 24R2 deprecation log, revised 20 February 2025, posted by the IFS Community account |
| Current plan (from February 2026) | Support reinstated in 25R2 service update 3, scheduled for 19 February 2026. It remains in 26R1 and is planned for removal in 26R2. | Posts by an IFS employee of 5 February and 27 May 2026 |
The 27 May 2026 post states that the legacy integration is still up for removal in 26R2 and that most standard operational reports have Report Studio based layouts in the 26R1 general availability release. These are employee posts in a community thread, not release notes, so the release documentation for your own version takes precedence. How service updates differ from release updates, which matters for the 25R2 reinstatement, is explained in service update vs release update.
The replacement for a Crystal report in IFS Cloud depends on what the report does, and the revised deprecation notice names a different tool for operational layouts than for ad-hoc reporting.
| Crystal object | Replacement named by IFS | What it means for the project |
|---|---|---|
| Operational report layout | IFS Report Studio | A layout rebuild per document. Check first whether your release ships a standard Report Studio layout for the same report. |
| Crystal Quick Report (ad-hoc) | Lobbies and lobby elements, or Power BI using BI Analysis Models | A redesign, not a copy. A lobby element or a Power BI view answers the same question in a different form. |
| Crystal kept after removal | Custom integration, for example through the External Reports Gateway | Your own integration to build, test at every update and support, with no standard IFS layer underneath. |
IFS documentation describes Report Studio as a web-based tool used to design layouts for operational reports, based on JSON data sources. Users need the FND_DESIGNER_REPORT permission set to launch it, and layouts are stored as .rep files. See the IFS Report Studio page in the IFS Cloud technical documentation. For ad-hoc reporting, the build steps for lobbies are covered in lobbies and custom dashboards in IFS Cloud.
Four decisions shape the Crystal exit, and each is cheaper to take before the first layout is redrawn.
The fourth decision belongs in the same inventory as extensions and modifications before each release, described in IFS Cloud upgrade readiness. Keeping rebuilt layouts inside the standard layout tools also keeps them out of the tailoring levels that need retesting at every update, explained in IFS Cloud tailoring levels.
Crystal exit projects go wrong when the plan treats every report as a one-to-one conversion into Report Studio.
If you want this sorted for your own report catalogue, the reporting and customisation work sits in my services for IFS Cloud.
The Crystal Reports integration in IFS Cloud is deprecated but still supported in 24R2, in 25R1 for upgrading customers with existing licences, in 25R2 from service update 3 and in 26R1. An IFS employee stated in the IFS Community in May 2026 that the integration is still planned for removal in 26R2.
IFS Report Studio replaces Crystal for operational report layouts in IFS Cloud, such as purchase orders, delivery notes and invoices. Report Studio is a web-based layout designer that uses JSON data sources, stores layouts as .rep files and requires the FND_DESIGNER_REPORT permission set.
The IFS Cloud deprecation notice revised on 20 February 2025 points ad-hoc Crystal Quick Reports to Lobbies and lobby elements, or to Power BI using BI Analysis Models. Report Studio is named for operational report layouts, not for ad-hoc reporting.
Keeping Crystal Reports with IFS Cloud after the removal planned for 26R2 requires a custom integration, for example through the External Reports Gateway, as an IFS employee wrote in the IFS Community in May 2026. That integration is customer-owned code that has to be tested at every IFS Cloud update.
The Crystal Reports dates in IFS Cloud changed because IFS revised the deprecation notice in February 2025 and then reinstated support in 25R2 service update 3. The first notice planned removal with 25R1, the revised notice made the integration unavailable in 25R2, and the current plan keeps it until removal in 26R2.
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 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 does the work, not a sales layer.
Selected clients from my IFS work: 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.
Send me the list, or the question you cannot answer yet. In a technical call we sort the reports into rebuild, redesign and retire, and set the date the Crystal exit has to meet in your upgrade plan.
Book a technical call about your Crystal reports See services for IFS Cloud