Skip to main contentSkip to footer

Time Fences in IFS Cloud: Demand and Planning Time Fence

How the demand and planning time fences work in IFS Cloud: what each protects, who sets the values, and how master scheduling and MRP react.

Independent IFS Cloud practice · Planning design Know where the plan is frozen and where the system may still change it The planning time fence and the demand time fence in IFS Cloud divide the planning horizon into periods in which master scheduling and MRP treat supply and demand differently. A planner who expects…

Read more

Master Production Schedule Level 1 in IFS Cloud Explained

How Master Production Schedule Level 1 works in IFS Cloud: Level 0 and Level 1 parts, the proposals it creates, dependent demand and time fences.

Independent IFS Cloud practice · Master scheduling design Describe the Level 0 and Level 1 structure before planners read the proposals Master Production Schedule Level 1 is the level of the IFS Cloud master schedule where you plan long-term demand for parts that are manufactured or purchased. Its calculation creates…

Read more

IFS Cloud Intraday Availability: Supply and Demand Timing

How IFS Cloud analyses short-term supply and demand down to the minute: the horizon, firm or non-firm items, balance fields and projected quantity.

Independent IFS Cloud practice · Short-term planning Check projected stock down to the minute for the next days IFS Cloud intraday availability is the analysis of the short-term supply and demand situation for inventory parts, considering the timings within the day down to minute level. It runs on the Inventory Parts…

Read more

Master Scheduling ATP in IFS Cloud: How Promising Works

How Master Scheduling Available to Promise works in IFS Cloud: the master schedule as data source, generic and customer-dimension checks, and set-up.

Independent IFS Cloud practice · Order promising design Decide what the master schedule promises before customer orders depend on it Master Scheduling Available to Promise (ATP) is a promising method in IFS Cloud that uses the master schedule (MPS) as the data source for customer order promising. A promise date from…

Read more

IFS Cloud Material Requisition: Statuses, Reserve, Issue

How IFS Cloud material requisition works for internal demand: statuses, reservation before issue, partial issue and closing a line.

Independent IFS Cloud practice · Internal demand design Decide who reserves, who issues and who closes before requisitions pile up An IFS Cloud material requisition is the document through which material is requested for internal demand, and it runs through its own flow: request, reservation, issue and closure. If the…

Read more

IFS Cloud Routing Lead Time: Fixed, Variable and Overlap

How IFS Cloud routing lead time is calculated: fixed and variable time, standard lot size, parallel operations and overlap, with worked examples.

Independent IFS Cloud practice · Manufacturing planning design Check your routing data against the calculation that produces the planned lead time IFS Cloud routing lead time is the lead time of a manufactured part calculated from its routing, and the page states that MRP and Master Scheduling use it. If the…

Read more

IFS Cloud Email Customer Documents: Set-Up Rules

IFS Cloud email customer documents: how the contact is found, what each of invoice, quotation and order confirmation needs, and the invoice lock.

Independent IFS Cloud practice · Sales output design Check the contact, the document and the event before customers say they never got the invoice To make IFS Cloud email customer documents reach customers, each document needs its own set-up: an invoice, a quotation and an order confirmation each have their own page…

Read more

IFS Cloud Lead Time: Purchase, Manufacturing and Expected

IFS Cloud lead time: how purchase, manufacturing and expected lead time are defined, where each is calculated and which one MRP reads.

Independent IFS Cloud practice · Planning data design Know which lead time a function reads before you fill the fields IFS Cloud lead time lives in several fields, and each field has its own meaning. If purchase, manufacturing and expected lead time are filled without knowing which one a function reads, planned dates…

Read more

IFS Cloud Multi-Supplier Ordering: How Splits Work

IFS Cloud multi-supplier ordering splits a requisition by percentage, rounds to standard multiples and warns against double sourcing. What to test.

Independent IFS Cloud practice · Purchasing design Split a requirement between suppliers on purpose, and check the quantities before the orders go out IFS Cloud multi-supplier ordering divides the quantity of one purchase requisition between suppliers by percentage. One supplier cannot or should not carry the whole…

Read more
Abstract illustration on a navy background with the article title: IFS Cloud SCM: where projects stall

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.

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.

  1. Planning parameters left at defaults. Purchase proposals then look random to buyers, who stop trusting them and order from spreadsheets.
  2. Reservation rules decided late. Warehouse teams find in UAT that the stock they expect to pick is reserved elsewhere.
  3. 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.
  4. 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.
  5. 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

×
Need Expert Guidance?
We've helped hundreds of businesses succeed. Get a free consultation to discuss your project requirements.
Get Free Consultation
17Years Experience
50Implementations
PRINCE2Certified
100%Success Rate

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.