Independent IFS Cloud practice · Supply chain implementation
IFS Cloud supply chain implementation that leaves purchasing, stock and shipping on standard functionality, ready for the next release
Key takeaways
- The implementation runs in six phases, and each phase ends in a written deliverable you keep: fit-gap list, configuration specification, interface register, report set, training material, cutover plan.
- Every requirement is placed in a fixed order: standard functionality first, then configuration, then the Extensibility Framework. Nothing is changed in the IFS core, so the setup stays update-safe.
- The link to finance is the configuration of postings and invoice matching inside IFS Cloud, tested with the finance owner. Links to CRM and logistics partners go through published projections and are entered in an interface register that names an owner for failed messages.
- Go-live is decided by rehearsed data loads and a signed readiness checklist, not by the date in the plan.
A supply chain implementation is judged months after go-live against three criteria. The first is whether purchasing, stock and shipping run on the same definitions at every site. The second is whether the setup survives the next R1 or R2 release without a retest of everything built around the standard. The third is whether buyers and planners work in IFS Cloud and not in a spreadsheet next to it. The choices that decide all three are made in the first weeks of the project, during process design.
I plan and run IFS Cloud supply chain implementations as an independent consultant. I have 18 years of hands-on work with IFS, from Apps 7.5 to IFS Cloud, with clients such as Fugro, LGC, BVI Medical, Betafence, Barlinek, NGK Ceramics, Newag and Oleofarm. The scope covers procurement, inventory, planning, production and logistics, and the sections below describe what is done in each phase and what you receive at the end of it.
1.Process analysis and design
The first phase documents how purchasing, goods receipt, inventory, planning and delivery work today, with the people who do the work, and finds where the current practice depends on a workaround. For example, a price may be kept in a spreadsheet because the supplier record cannot hold it, an approval may be done by email, or a receipt may be booked late because the warehouse has no terminal at the dock.
What happens
Each flow is walked through step by step and compared with IFS Cloud standard functionality. Every gap is assigned to one of four outcomes: standard functionality covers it, configuration covers it, an extension inside the Extensibility Framework is justified, or the requirement is dropped because the process can change instead. Extensions follow the Clean Core rule, so they are additive and do not alter standard packages.
What you receive
- As-is and to-be process maps - one per flow, for example purchase-to-pay, order-to-delivery, replenishment.
- Fit-gap list - each requirement with its outcome (standard, configuration, extension, dropped) and the reason.
- Decision log - the process choices the business owners signed off, with the date and the owner.
2.Module configuration
Configuration is done from the fit-gap list, area by area, in a test environment that holds a copy of the client’s own master data. The areas below are configured against the agreed to-be processes. Where a site or legal entity needs a different value, the difference is recorded as an explicit exception to the shared template.
| Area | What is configured | Deliverable |
|---|---|---|
| Procurement | Purchase requisition and order flow, approval rules, supplier and purchase part data, price and receipt-matching settings. See also centralised purchasing in IFS Cloud. | Procurement configuration specification and approval matrix |
| Inventory | Warehouse and location structure, inventory part setup, receipt and issue handling, cycle counting. | Inventory configuration specification and master data rules |
| Demand and supply planning | Planning parameters per part, lead times, safety stock and reorder settings, MRP controls. | Planning parameter sheet and planning-run test results |
| Production | Product structures, routings and shop order handling to the depth the client uses. | Production configuration specification |
| Logistics | Customer order delivery, picking, packing and shipment handling, including consolidated shipments where they apply. | Logistics configuration specification and shipping document set |
3.Integrations with finance, CRM and logistics partners
Inside IFS Cloud, the link between procurement, inventory and finance is configuration: how receipts, supplier invoices and stock movements post, and how invoices are matched to orders and receipts. That configuration is tested with finance in the same test cycle as the supply chain processes, because a setup error in the supply chain shows up as a wrong posting.
Links to systems outside IFS Cloud, such as the client’s CRM and carrier or warehouse partners, are built on published projections (OData and REST) and not on internal views. Orchestration stays outside IFS where possible, so the logic does not become one more object to retest at each release. See IFS Cloud Workflows for what is done inside the system.
What you receive
- Interface register - each interface with direction, data, trigger, frequency, and a named owner for failed messages.
- Interface specifications and test results - including the error cases: rejected message, timeout, duplicate.
- Finance posting test results - signed off by the finance owner.
4.Analytics, reporting and exception monitoring
Reporting is agreed before go-live, and the baseline is taken from the old system while it is still running. I ask the client to choose two or three measures that the business was already discussing, for example on-time supplier delivery or stock accuracy, and each measure gets a definition, a source in IFS Cloud and an owner. A benefit that was never baselined cannot be shown afterwards.
Reports and notifications are built with the tools that IFS Cloud maintains for you: Quick Reports for lists and extracts, Lobby elements for work queues, and Custom Events with Workflows where a business event needs a notification or an approval route. Each one is entered in a report and alert specification with its purpose, its owner and the action the recipient is expected to take.
Some supply chain problems create no error in the system: a purchase order the supplier never confirmed, a receipt that was never invoiced, a supplier price that moved between two orders. A Custom Event reacts when a row changes, so it cannot detect something that stays unchanged. These cases need a scheduled check. For a read-only check, the SCM Automation Pack reads standard OData projections with a read-only integration user. No object is created in the client’s IFS, so a release update leaves nothing of ours for the client to test, and we check that our projection reads still match the new release as part of the subscription. The SCM Exception Scan shows what such a check finds in your own data in five business days, before any ongoing commitment.
What you receive
- Report and alert specification - purpose, owner, recipient action, source.
- Measure definitions with baselines - taken before go-live.
- The built reports, lobby elements, Custom Events and Workflows - tested against real data.
5.User training and adoption
Training is organised by role: buyer, planner, warehouse operator, shipping clerk, approver. Each role is trained on the client’s own configured system and its own part and supplier data, following the process maps from phase 1, so the exercise is the real daily task and not a generic demonstration. Key users are trained first and take part in acceptance testing, which makes them the first line of support at go-live.
What you receive
- Training plan by role - who is trained, on which process, in which order.
- Step-by-step guides - written from the agreed processes, one per task.
- Acceptance test scripts and sign-off - run by key users, with defects logged and closed.
6.Go-live and post-implementation support
The go-live date depends on data migration, because every rejected record has to be corrected at the source or in the mapping. The load is therefore rehearsed several times on a schedule, with a defined cut of source data each time. The rehearsals end when the list of rejected records is closed, or when the data owner has accepted each remaining rejection in writing. IFS Cloud enforces its business rules at load time, which means validation is a deliverable with its own sign-off. See the data migration plan for the approach.
The go or no-go decision is taken against a written readiness checklist that covers data (rejection list closed or accepted by the data owner), interfaces, testing, training and support. After go-live, I stay with the team for an agreed hypercare period, resolve issues against the decision log and configuration specifications, and hand over to the client’s support organisation with documented known issues.
What you receive
- Cutover plan and checklist - sequence, owners, timing, and a fallback plan.
- Migration rehearsal reports - what loaded, what was rejected, why.
- Go-live readiness decision - signed by the business owners.
- Handover to support - open items, known issues, and the configuration record.
The templates for these documents are available separately in the implementation documentation kit if your own project team prefers to run the delivery.
7.Frequently asked questions
What does an IFS Cloud supply chain management implementation cover?
An IFS Cloud supply chain implementation covers process analysis, configuration of procurement, inventory, planning, production and logistics, integrations with finance, CRM and logistics partners, reporting, user training, and go-live with post-implementation support. Each of the six phases ends in written deliverables such as a fit-gap list, a configuration specification, an interface register and a cutover plan.
Do you modify IFS Cloud core to meet supply chain requirements?
No. The IFS core is not modified. Each requirement is checked against standard IFS Cloud functionality, then against configuration, then against the Extensibility Framework with Custom Fields, Custom Events and Workflows. Because nothing in the core is changed, there is no modified core code to retest at the R1 and R2 releases.
How long does an IFS Cloud supply chain implementation take?
I do not quote a duration before the process analysis is done. The number of sites and legal entities, the number of interfaces, and the volume and quality of the data to migrate set the timeline more than the list of modules does. The plan with dates is a deliverable of the first phase.
Can supply chain exception monitoring be added to an IFS Cloud implementation without installing anything in IFS?
Yes. The SCM Automation Pack reads standard OData projections with a read-only integration user and creates no object in the client’s IFS, so a release update leaves nothing of ours for the client to test. We check that our projection reads match the new release as part of the subscription. The SCM Exception Scan shows the exceptions in your own data in five business days, with no notification sent during the scan.
8.About the author
Dariusz Myśliwiec: 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 through an independent practice.
Selected clients: Fugro · LGC · BVI Medical · Betafence · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Planning an IFS Cloud supply chain implementation?
Send me the sites, modules and interfaces in scope. A 30-minute technical call is enough to say which phases you need and where the risks sit. You talk to the consultant who does the work.
