Supply chain in IFS Cloud · Implementation design
IFS Cloud SCM: the process chain, the design decision in each area, and where projects stall
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
- The SCM scope in IFS Cloud is a chain: a customer order consumes or triggers supply, supply comes from planning and purchasing, the warehouse reserves and picks, the shipment delivers, and every step posts to finance.
- Each area has a small number of design decisions that are expensive to change after go-live, for example reservation rules, the planning method per part, warehouse structure and posting control.
- Projects stall at the hand-offs between areas, because each workstream tests its own screens and nobody tests the chain end to end with finance.
- AI functions such as IFS.ai Copilot assistants for supplier quotations and the 25R2 Digital Workers work on the same records, so they inherit the quality of the SCM design.
1.Which process areas make up IFS Cloud SCM?
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.
2.What should be decided in each area before configuration starts?
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.
- Order flow: which customer order types exist and what each one does automatically. See customer order types in IFS Cloud and order promising the plan can keep.
- Planning: classify parts before calculating reorder points or safety stock. See reorder points in IFS Cloud and IPR safety stock models.
- Sourcing: how an order line finds its supply, from stock, a purchase order or another site. See IFS Cloud sourcing rules.
- Warehouse: design locations from the physical floor, then decide which stock is reserved first. See warehouse structure in IFS Cloud and reservation rules.
- Tracking: track lots and serials only where someone uses the information. See lot and serial tracking decisions.
- Multi-site: decide what sites share and what they keep apart. See IFS Cloud site clusters and multi-site implementation lessons.
- Finance link: agree the posting for each warehouse transaction with finance. See posting control in IFS Cloud.
3.Where do SCM projects in IFS Cloud stall?
SCM projects in IFS Cloud stall where one workstream's setting becomes another workstream's problem, and these hand-offs follow a recognisable pattern.
- Planning parameters left at defaults. Purchase proposals then look random to buyers, who stop trusting them and order from spreadsheets.
- Reservation rules decided late. Warehouse teams find in UAT that the stock they expect to pick is reserved elsewhere.
- Corrections without a rule. Users undo deliveries that should have been returns, and stock in the system drifts from the shelf. The difference is explained in undo customer delivery in IFS Cloud.
- Postings tested last. Finance sees the inventory postings for the first time in the final test cycle, and every mapping error means a change in configuration and a retest.
- Night jobs designed for the good night. Planning runs and reservation jobs run in background queues, and nobody owns them when they fail. See IFS Cloud background jobs.
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.
4.How do AI and exception monitoring fit into the supply chain design?
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.
5.Frequently asked questions
What does IFS Cloud SCM include?
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.
Which supply chain settings in IFS Cloud are hardest to change after go-live?
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.
Why do supply chain implementations in IFS Cloud stall?
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.
Does IFS Cloud use AI in supply chain processes?
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.
Where should an IFS Cloud SCM implementation start?
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.
6.About the author
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.
Which hand-off in your supply chain fails first?
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
