Abstract illustration on a navy background with the article title: IPR Safety Stock Models in IFS Cloud: How Each One Works

IPR Safety Stock Models in IFS Cloud: How Each One Works

Details
Created: 29 October 2026
Last Updated: 08 November 2026
  • IFS Cloud
  • Inventory
  • Planning
  • IFS Cloud Implementation
  • Best Practices

Independent IFS Cloud practice · Inventory planning design

Choose a safety stock model you can explain to the buyer

IFS Cloud IPR safety stock is the inventory kept on stock as a buffer to achieve the wanted service level, and the model that calculates it decides how the buffer follows demand. If the model is chosen without a decision, the buffer cannot be explained to a buyer, or it grows without a limit. The stake is stock held against a service level that nobody chose, or a service level that the buffer does not deliver. This article follows the 26R1 documentation page on IPR safety stock models (titled IPR Time Phased Safety Stock Models), and two 25R2 pages where it says so.

Key takeaways

  • The Demand Model offers Yearly Prediction, History and Forecast, and the Safety Stock Model offers Manual, Time Coverage, Historical uncertainty and Mean Absolute Error.
  • Time Coverage multiplies the forecast per day from the Demand Model by the Safety Stock Cover Time; the page’s example is a yearly demand of 876 and a cover time of 25, which gives a safety stock of 60.
  • Historical uncertainty multiplies the normal inverse of the service rate by the standard deviation of issues in lead time, and Mean Absolute Error takes the deviation from the forecast in Demand Planning.
  • The parameter Max Safety Stock Cover Time, set in the planning hierarchy, limits the safety stock so that it does not get extremely large.
  • IPR can be used on parts with planning method B, and on parts with planning methods A, D, E, F, G and M, where it computes the safety stock only.
  • Period-based safety stock is a separate concept, described on a 25R2 page, and is put on top of regular safety stock only during the defined periods.

1.What does IPR calculate when it calculates safety stock?

The result of the IPR calculation is how much inventory should be kept on stock as a buffer to achieve the wanted service level. The result is written to the Safety Stock field of the inventory part, or to a tab on Inventory Part/Planning Data/General. You can see all the detailed calculations in an Excel sheet, if you access the sheet by right-clicking on the Inventory Part/Planning Data/IPR Parameters tab. The classification of parts and the rule hierarchy of IPR are covered in reorder points in IFS Cloud and are not repeated here.

2.Which demand models can feed the calculation?

The Demand Model has three options. Yearly Prediction simply uses the field Pred Year Cons Qty on the inventory part as the yearly demand for the part. History uses the Lead Time, Cycle Time, No of Issues in Lead Time and the Avg. Qty per Issue to compute the yearly demand. The page gives no further description of the third option, Forecast.

3.Which safety stock models exist, and how does each work?

The Safety Stock Model has four options, and the table gives the formula the page prints for each one.

Model What the page says
Manual Listed as an option; the page gives no calculation for it
Time Coverage Safety Stock = Forecast (day) determined by the Demand Model * Safety Stock Cover Time
Historical uncertainty Safety Stock = NORMINV(Service Rate) * Standard Derivation Issues in Lead Time; the Standard Derivation is computed by the Analyze Demand Derivation background job
Mean Absolute Error Similar to Historical uncertainty, with the important difference that the Standard Derivation is fetched from the forecast in Demand Planning; the printed formula is Safety Stock = NORMINV(Service Rate) * SQRT(MSE in Forecast Period)

The Time Coverage example on the page: with a yearly demand of 876 and a Safety Stock Cover Time of 25, the safety stock is 876 / 365 × 25 = 60.

The Mean Absolute Error model is named for an absolute error, while the formula on the page uses MSE. The 25R2 copy of the page also says MSE: the Standard Derivation is computed from the MSE error for the lead time (plus eventual cycle time) from Demand Planning. This article reports both as printed and does not resolve the difference; confirm in your release which error measure the calculation uses before the model is chosen for a part class.

For Historical uncertainty, the 25R2 page on IPR models describes a wider version than the 26R1 page: Total Standard Derivation = Standard Derivation measured in the lead time + Standard Derivation in the lead time length, where the lead time length Standard Derivation is computed by the Calculate Purchased Lead Time background job. The 26R1 page has one deviation and one job. Name the page you rely on when you document the model. Lead time definitions are covered in lead times in IFS Cloud.

4.What limits the buffer?

There exists a parameter called Max Safety Stock Cover Time, set in the planning hierarchy and used to limit the safety stock so that it does not get extremely large. The page calls this especially useful when using a service level controlled safety stock model, where unnaturally high transactions that are not marked as abnormal result in high safety stocks. The ageing of stock held in a buffer is analysed in the anatomy of stock aging.

5.Which parts can use it?

IPR can be used on parts with planning method B. IPR can also be used for parts with planning methods A, D, E, F, G and M, and it then computes the safety stock only. The page prints the letters without saying what they stand for, so the mapping to your planning methods is checked in the system before the part classes are assigned. Stock that reacts to exceptions is covered in reactive inventory management.

6.What is period-based safety stock, and how does it differ?

The 25R2 page on Time Phased Safety Stock describes a period based safety stock to meet peaks in demand, or periods where lack of capacity occurs. It is put on top of regular safety stock if it is used, but is done only during the periods defined. If the part is handled by MS, the end date of the period must be outside the planning time fence date of the master schedule level 1 part when it is entered. It is not applicable in combination with project MS or project MRP. The 26R1 master scheduling messages page includes the message “Projected balance is below time phased safety stock”, generated when the projected balance falls below the time phased safety stock defined for the period.

The 26R1 page on IPR safety stock models does not describe periods, peaks or capacity gaps. It uses the words “Time Phased Safety Stock” in its title, as the name of the calculation, and for a destination of the result, and describes the models above. The models in this article are therefore not period-based safety stock.

7.Who signs off the service level?

Which number would a buyer quote if asked why a part carries this buffer? The formulas of the service level models contain the service rate, so someone has to set it, and the planner and the buyer agree it per part class. The same people decide the Max Safety Stock Cover Time in the planning hierarchy, because it caps the buffer that the model produces. The planning lead reviews the choice of model per part class, and records which page, 25R2 or 26R1, the documentation of Historical uncertainty relies on. The review interval is a business decision, as the page gives none.

8.How do you test a model before go-live?

Test with one part per model and the same demand history, and write down the expected buffer before each calculation.

Scenario Expected buffer Owner
Time Coverage, yearly demand 876, cover time 25 60, as 876 / 365 × 25 (the page’s example) Planner
Manual Record the buffer; the page gives no calculation Planner
Historical uncertainty NORMINV(Service Rate) * Standard Derivation Issues in Lead Time; record the result of the Analyze Demand Derivation job first Planner
Mean Absolute Error NORMINV(Service Rate) * SQRT(MSE in Forecast Period); record which error measure the release uses Planner
Model that produces a very large buffer, with Max Safety Stock Cover Time set Buffer limited by the cover time parameter; record both values Planning lead
Part with planning method B and part with planning method A IPR available on B; on A it computes the safety stock only Planning lead

9.What does a safety stock model checklist contain?

The safety stock set-up is ready for go-live when each check below has a record behind it.

  1. The demand model and the safety stock model are decided per part class.
  2. The service level behind each service-level model is signed off by planning and purchasing.
  3. Max Safety Stock Cover Time is set in the planning hierarchy.
  4. The planning methods of the parts are checked against the methods the page lists.
  5. The choice for Mean Absolute Error and Historical uncertainty names the documentation page it relies on.
  6. The six test scenarios are recorded with evidence.

10.Frequently asked questions

How does IFS Cloud IPR calculate safety stock?

The IFS Cloud IPR calculation returns how much inventory should be kept on stock as a buffer to achieve the wanted service level. The Demand Model offers Yearly Prediction, History and Forecast, and the Safety Stock Model offers Manual, Time Coverage, Historical uncertainty and Mean Absolute Error.

What is the difference between the Historical Uncertainty and Time Coverage models?

In IFS Cloud IPR, Time Coverage calculates the safety stock as the forecast per day determined by the Demand Model multiplied by the Safety Stock Cover Time. Historical uncertainty calculates it as NORMINV of the service rate multiplied by the standard deviation of issues in lead time, which the Analyze Demand Derivation background job computes.

What does the Max Safety Stock Cover Time limit do?

Max Safety Stock Cover Time is a parameter set in the IFS Cloud planning hierarchy that limits the safety stock so that it does not get extremely large. The documentation calls it especially useful with a service level controlled model, where unnaturally high transactions not marked as abnormal result in high safety stocks.

Which planning methods can use IPR for safety stock?

IPR in IFS Cloud can be used on parts with planning method B. It can also be used for parts with planning methods A, D, E, F, G and M, and it then computes the safety stock only.

What is time phased safety stock?

Time phased safety stock in IFS Cloud is a period based safety stock to meet peaks in demand, or periods where lack of capacity occurs. It is put on top of regular safety stock if it is used, but is done only during the periods defined.

11.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Can you explain your safety stock numbers to the buyer?

A review of the safety stock models by part class, with the planner and the buyer, shows which model and which service level sit behind each buffer.

Book a safety stock review Read about reorder points

Abstract illustration on a navy background with the article title: Handling Units and Packing Instructions in IFS Cloud

Handling Units and Packing Instructions in IFS Cloud

Details
Created: 29 October 2026
Last Updated: 08 November 2026
  • IFS Cloud
  • Delivery
  • Warehousing
  • IFS Cloud Implementation
  • Best Practices

Independent IFS Cloud practice · Shipping and packing design

Design the packing instruction once, so every pallet is described the same way

A handling unit in IFS Cloud is a collective name for all types of containers in which parts can be packed, and a handling unit structure describes the packing as done in one or several levels for pallets, boxes and parts. If the structure is built by hand for each shipment and no packing instruction is designed, the content of a pallet and the labels on it differ between shipments. The stake is handling unit structures, SSCC numbers and labels that do not match the physical shipment. This article follows the 26R1 page on handling units, whose body text is identical in the 25R2 tree, and the activity pages on packing instructions, SSCC and labels.

Key takeaways

  • Packing can be performed manually or automatically, and a predefined packing instruction can build up the entire handling unit structure from the bottom up, including handling unit accessories.
  • A packing instruction is a template for how handling units are connected; the first node entered becomes the root node, and a packing instruction can only have one root node.
  • Packing according to a packing instruction first packs the part by handling unit capacity for the handling unit type on the lowest level, and then applies the parent levels.
  • A handling unit is identified internally by a unique ID; an SSCC or an alternative label can be added.
  • For automatic packing, it is only the Mix of Lot Batch Numbers Blocked option that has an effect, and only when it is enabled on the lowest level.
  • Serial tracked or Lot/Batch tracked parts cannot be used as Packaging Material Parts.

1.What is a handling unit, and what does the structure describe?

A handling unit is a container in which parts can be packed, and a handling unit structure describes the packing across one or several levels for pallets, boxes and parts. The page states that you should not use the handling unit functionality if you are not labelling the handling unit with a unique identifier. For different pack sizes of a part with the same GTIN, it says the Input UoM functionality should be used instead.

The handling unit capacity is defined for a part (or storage requirement group) and a unit of measure. The page gives the example that the capacity for a part could be 100 pcs on a pallet, while the same part with 10PK as unit of measure on another site could have a capacity of 10 "10PK".

2.How is packing done, manually and automatically?

The packing process can be performed either manually or automatically. It is also possible to pack according to a predefined packing instruction, building up the entire handling unit structure from the bottom up, including handling unit accessories.

The default packing instruction can be set for a capacity requirement group, for a global part number, a part number/site, a part number/site/customer or a part number/site/customer/address combination. In the shipment type it can be defined that pack according to packing instruction is performed at the execution of a main activity in the shipment flow, for example reservation, report picking or delivery. For inventory, the part to be packed must have handling unit = 0 and have a quantity available, and pack according to packing instruction must be applied on records stored in the same location.

3.What is a packing instruction?

A packing instruction defines how one or more handling units are connected to each other, and can be described as a template informing the user how to pack. The first node entered becomes the root node, and a packing instruction can only have one root node. At least one handling unit type must be defined in the basic data. The nodes are connected to each other with the parent node field, or the connection to the parent is made automatically with the Add Sub Handling Unit option. The user can define that the packing should be filled up with empty handling units.

The Handling Units page gives an example of a packing instruction, shown in the table.

Level Handling unit Content in the example
Top Pallet Four big boxes can be stored on the pallet
Middle Big box Two small boxes can be stored in each big box
Lowest Small box The reference to the part is made through the handling unit capacity for the lowest level handling units

Per level of the packing instruction it is also possible to define rules regarding a mix of parts, lot batches or condition codes. These rules are validated when performing manual packing.

4.How does packing according to a packing instruction proceed?

The Pack According to Packing Instruction activity first packs the part according to the handling unit capacity for the handling unit type defined on the lowest level of the chosen packing instruction. The parent levels in the packing instruction are applied afterwards. The page on handling units adds that the associated packaging material parts are consumed (issued) from a location using the same backflush principle as in manufacturing. For a handling unit type with additive volume, the volume of the handling unit is dynamic and defined by the content attached to it.

The packing proposal is a separate tool and is described in the IFS Cloud packing proposal. The shipment order that carries the packed handling units is described in the shipment order in IFS Cloud, and consolidation of deliveries in consolidated shipment in IFS Cloud.

5.How are handling units identified?

The handling unit is identified internally via a unique handling unit ID. Alternative identification can be achieved via an SSCC, which can be created for all levels, and another option is to create an alternative handling unit label.

The page on creating an SSCC for a handling unit adds the prerequisites: the company prefixes and extension digits for each handling unit type should be predefined, and the Generate SSCC option should, in some scenarios, be enabled. The page does not say which scenarios. The SSCC is printed on the handling unit label, the handling unit content label and the shipment handling unit label, and it can also be sent using the EDI message service.

6.How are labels printed?

The setting for printing shipment handling unit labels can be maintained on the handling unit type and in the packing instruction. It is possible to print a label for a specific handling unit no matter whether the Print Shipment Handling Unit Label setting is enabled or not. The shipment handling unit label contains information about sender address, receiver address, transport instructions, delivery note number, number of handling units and the total weight for the handling units. Scanning and label work at the dock are covered in warehouse data collection design, and the documents created by shipping in shipping goods and assets in IFS Cloud.

7.How do tracked parts and mixed lots behave in handling units?

When parts are packed manually, it is allowed to mix different parts, lot batches and serials. For automatic packing, only the Mix of Lot Batch Numbers Blocked option has an effect, and only when it is enabled on the lowest level. Serial tracked or Lot/Batch tracked parts cannot be used as Packaging Material Parts. The decisions on tracked parts themselves are in lot and serial tracking decisions in IFS Cloud.

8.Who designs the packing instruction?

A template that nobody at the dock recognises produces structures that nobody can reproduce. The dock lead and the shipping coordinator define the handling unit types and the levels of each instruction, because they know how a pallet is built and which boxes sit in it. Warehouse and quality decide the mix rules per level and whether the Mix of Lot Batch Numbers Blocked option is enabled on the lowest level. Shipping decides where the print setting is kept, on the handling unit type or in the packing instruction. Whoever owns the company prefixes decides the prefixes and extension digits for each handling unit type, because the SSCC needs them. The default packing instruction is assigned by the owner of the part master at one of the five key levels the page lists.

9.How do you test packing before go-live?

Test with one shipment per packing instruction, and write down the expected structure, SSCC and label before packing.

Scenario Expected result Owner
Pack according to the three-level example instruction Lowest level packed first by handling unit capacity, then the parent levels Dock lead
Part to pack has a handling unit other than 0 or no quantity available Prerequisite not met; record the result Dock lead
Instruction with fill-up with empty handling units Packing filled up with empty handling units Dock lead
Create an SSCC for a handling unit type without prefix and extension digits Prerequisite not met; record the result Shipping coordinator
Print a label for one handling unit with the print setting disabled The label can be printed Shipping coordinator
Automatic packing of two lots, option Mix of Lot Batch Numbers Blocked enabled on the lowest level Lots are not mixed Warehouse lead
Manual packing of two lots in one handling unit Allowed, unless a mix rule on the level blocks it Warehouse lead

10.What does a handling unit set-up checklist contain?

The handling unit set-up is ready for go-live when each check below has a record behind it.

  1. Handling unit types are defined in the basic data, with capacity per part and unit of measure.
  2. Each packing instruction has one root node and its levels are written down.
  3. Default packing instructions are assigned at the key levels that are used.
  4. The shipment type that runs pack according to packing instruction is decided.
  5. Company prefixes and extension digits exist for each handling unit type that needs an SSCC.
  6. The label print setting is decided on the handling unit type and in the instruction.
  7. The seven test scenarios are recorded with evidence.

11.Frequently asked questions

What is a handling unit in IFS Cloud?

A handling unit in IFS Cloud is a collective name for all types of containers in which parts can be packed. The purpose of a handling unit structure is to describe the packing as done in one or several levels for pallets, boxes and parts.

What is a packing instruction?

A packing instruction in IFS Cloud defines how one or more handling units are connected to each other, and can be described as a template informing the user how to pack. The first node entered becomes the root node, and a packing instruction can only have one root node.

In which order does packing according to a packing instruction build a handling unit structure?

Pack According to Packing Instruction in IFS Cloud first packs the part according to the handling unit capacity for the handling unit type on the lowest level of the chosen packing instruction. The parent levels of the packing instruction are applied after that.

What does an SSCC need to be created?

To create an SSCC for a handling unit in IFS Cloud, the company prefixes and extension digits for each handling unit type should be predefined. The Generate SSCC option should also, in some scenarios, be enabled; the documentation does not list the scenarios.

Can tracked parts be used as packaging material?

Serial tracked or Lot/Batch tracked parts cannot be used as Packaging Material Parts in IFS Cloud handling units.

12.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Are your pallets and boxes described differently from one shipment to the next?

A review of handling unit types and packing instructions against the way your dock packs shows which levels, labels and SSCC settings need a decision.

Book a packing instruction review Read about lot and serial decisions

Abstract illustration on a navy background with the article title: Part Status in IFS Cloud: Onhand, Demand and Supply Flags

Part Status in IFS Cloud: Onhand, Demand and Supply Flags

Details
Created: 29 October 2026
Last Updated: 07 November 2026
  • IFS Cloud
  • Inventory
  • Supply Chain Data Integrity
  • IFS Cloud Implementation
  • Best Practices

Independent IFS Cloud practice · Master data design

Design the part status set before parts are linked to it

An IFS Cloud part status is a master data record that describes the different phases of a part and controls the extent to which the system can use the part. Its parameters cannot be modified once the record is created, and a code linked to any part cannot be removed, so the set has to be designed before parts are linked. This article follows the 26R1 page on adding or modifying a part status.

Key takeaways

  • A part status has three columns: Quantity On Hand, Demand and Supplies, and each column carries one setting per status code.
  • If inventory still exists for a part, it cannot have a part status of Onhand Not Allowed.
  • An inventory part must have the setting Demands Allowed to be used as a sales part, and parts linked to a code with Supplies Allowed can be purchased and received.
  • The predefined status code is A, Active, with Onhand Allowed, Demands Allowed and Supplies Allowed; it cannot be deleted or modified and is the default for new inventory parts.
  • Once a record is created, its parameters cannot be modified, and a code linked to any part cannot be removed.

1.What is a part status in IFS Cloud, and where is it set?

Part status describes the different phases of the parts, and this controls the extent to which the part can be used by the system. The status is set for each part on the Inventory Part page. Defining the status codes is a task for a system administrator or an equivalent person.

2.What do the three columns control?

Each status code carries one setting in each of three columns, with the effects and defaults below.

Column What the page says Default
Quantity On Hand Indicates whether or not a part can have a quantity on hand; if inventory still exists for a part, it cannot have a part status of Onhand Not Allowed Onhand Allowed
Demand Indicates whether or not demands are allowed; an inventory part must have the setting Demands Allowed for it to be used as a sales part Demands Allowed
Supplies Indicates whether or not supplies are allowed; with Supplies Allowed, parts linked to the code can be purchased and received, otherwise they cannot Supplies Allowed

3.What is the predefined status?

The predefined status code is A, Active, and this code cannot be deleted or modified. The default settings for Active part status are Onhand Allowed, Demands Allowed and Supplies Allowed. The system installed part status A, Active, defaults for each new inventory part record, and the status of a part can be changed on the Inventory Part page.

4.Which rules limit changes to statuses?

Once a status record is created, the parameters cannot be modified. If any parts are linked to a part status code, that code cannot be removed. A wrong combination in a created status therefore cannot be corrected by editing it, and the set has to be agreed before parts are linked. The loading of parts is planned in the IFS Cloud data migration plan, with a checklist in the data migration checklist.

5.How can combinations model a part lifecycle?

The page states that you could set up codes, for example, for experimental, obsolete or replacement parts. As an example for obsolete parts, it describes reducing the quantity of obsolete parts by allowing demand but no longer allowing supplies.

The page adds one effect outside the three columns: MRP and PMRP will consider the demands only when the On Hand Qty, Demand and Supplier parameters of the part are set to Onhand Allowed, Demands Allowed and Supplies Allowed respectively. Part numbering is a separate master data decision, covered in the IFS Cloud part numbering scheme, and the place of master data in a project is described in the IFS Cloud ERP implementation guide.

6.Which decisions belong to master data owners, sales and purchasing?

Three decisions need a named owner. The master data owner decides which status codes exist, because a created code cannot be modified. Sales and purchasing decide with the master data owner which phases of a part need a code, because Demands Allowed controls use as a sales part and Supplies Allowed controls purchase and receipt. The administrator, or an equivalent person, enters the codes, and the master data owner decides who may assign a status to a part on the Inventory Part page. A status is a separate setting from the availability control, which acts on stock records and is covered in part availability control settings.

7.How do you test the statuses before go-live?

Test each status with one part and the function it restricts, and write down the expected block or permission before each attempt.

Scenario Expected result Owner
Part with inventory, change to a status with Onhand Not Allowed Not possible while inventory exists Master data owner
Part with a status without Demands Allowed, use as a sales part Not allowed; the part must have Demands Allowed Sales
Part with a status without Supplies Allowed, purchase and receive Not possible; parts can be purchased and received only with Supplies Allowed Purchasing
Modify the parameters of a created status Not possible Administrator
Remove a status code that has parts linked Not possible Administrator
Create a new inventory part Status A, Active, is the default Master data owner

8.What does a part status checklist contain?

The part status set is ready for go-live when each check below has a record behind it.

  1. The status codes that exist are written down, with the setting of each of the three columns.
  2. Each code is agreed with sales and purchasing before parts are linked to it.
  3. Someone is named to assign statuses on the Inventory Part page.
  4. The use of status A, Active, as default for new inventory parts is accepted.
  5. The six test scenarios are recorded with evidence.

9.Frequently asked questions

What is a part status in IFS Cloud?

A part status in IFS Cloud describes the different phases of a part and controls the extent to which the part can be used by the system. Each status code has three settings: Quantity On Hand, Demand and Supplies.

Why can I not give a part with stock the status Onhand Not Allowed?

In IFS Cloud, if inventory still exists for a part, the part cannot have a part status of Onhand Not Allowed. The Quantity On Hand column indicates whether or not a part can have a quantity on hand.

What does Demands Allowed control?

Demands Allowed in an IFS Cloud part status indicates that demands are allowed for the part. An inventory part must have the setting Demands Allowed to be used as a sales part. MRP and PMRP consider the demands only when the part is set to Onhand Allowed, Demands Allowed and Supplies Allowed.

Can I change a part status record after it has been created?

Once a part status record is created in IFS Cloud, its parameters cannot be modified. If any parts are linked to a part status code, that code cannot be removed. The status of an individual part can be changed on the Inventory Part page.

What is the default part status for a new inventory part?

The default part status for a new inventory part in IFS Cloud is A, Active, which is installed by the system. Active allows Onhand, Demands and Supplies, and the code cannot be deleted or modified.

10.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Are parts blocked and nobody knows which status does it?

A review of the status set against the part lifecycle your business uses shows which flags block which parts.

Book a part status review Read about availability controls

Abstract illustration on a navy background with the article title: Reservation Rules in IFS Cloud: Which Stock Goes First

Reservation Rules in IFS Cloud: Which Stock Goes First

Details
Created: 29 October 2026
Last Updated: 07 November 2026
  • IFS Cloud
  • Warehousing
  • Inventory
  • IFS Cloud Implementation
  • Customer Orders

Independent IFS Cloud practice · Reservation design

Set the reservation rule order to match the stock the warehouse wants to ship first

IFS Cloud reservation rules decide which stock record is reserved when several records could cover the same order line. The IFS page on reservation management lists five priority rules, and the setup on the site decides which of them apply. If nobody reviewed that setup, the receipt, expiration date, putaway zone or handling unit that leaves the warehouse first is chosen by a configuration list that nobody owns. This article follows the 26R1 page on reservation management, whose text is identical in the 25R2 tree.

Key takeaways

  • The page lists five priority rules: Earliest Expiration Date, Earliest Receipt Date, Highest Putaway Zone Ranking, Largest Quantity on Handling Unit and Outermost Handling Unit.
  • It is possible to define the order of these rules and also skip some of them if not considered important; the page ties the rules to the setup on the site.
  • On a customer order line, the quantities assigned to shipment lines are reserved first, starting with the oldest shipment, and then the quantity not assigned to any shipment.
  • Manual reservations by the user always have priority over the set rules; that statement is about the rules and does not say that a manual reservation is always possible.
  • If handling unit optimization is used, automatic reservation always tries to reserve complete handling units first, regardless of the priority setting.
  • Automatic reservation runs as a background job, so the user receives no immediate response; lines that did not get fully reserved are followed up on the Handle Customer Order Shortages page.

1.When does IFS Cloud reserve stock automatically?

Automatic reservation applies the priority rules only if all the prerequisites on the reservation management page are fulfilled. Among them, the inventory location must be a picking location, the part must not be expired (that is, the part must be current), and if the inventory part is connected to a part availability control ID, the availability control shall allow reservations. Lines that are left without coverage are described in sales orders without coverage in IFS Cloud, and the settings of the availability control in part availability control settings.

The 25R2 page on reserving customer orders adds that, in addition to reserving with the automatic reservation logic order by order, you can reserve line by line, shipment by shipment, or via a batch job.

2.Which reservation rules exist, and in what order are they applied?

The reservation functionality could use any of five priority rules, depending on the setup on the site. The page lists them in the sequence of the table, and the list is complete.

Rule What the page says
Earliest Expiration Date The part is reserved at the location where the part has the earliest expiration date
Earliest Receipt Date The part is reserved at the location where the earliest receipts of the part has been performed
Highest Putaway Zone Ranking Defined on the page in one line; read it there before you set the order
Largest Quantity on Handling Unit Defined on the page in one line; read it there before you set the order
Outermost Handling Unit The parts are reserved in handling units which have as few parents as possible

It is possible to define the order of these rules and also skip some of them if not considered important. The page says only that this is part of the setup on the site. It does not name the screen where the order is set or who sets it. The 25R2 page on reserving customer orders names Site/Warehouse Management/Automatic Reservation as the page for the handling unit setup, and does not say that the rule order is set there.

3.What changes the effect of a rule on handling units?

For a handling unit, the expiration date and receipt date use the worst case value for the content of the handling unit.

If handling unit optimization is used, the automatic reservation will always try to reserve parts in complete handling units first, regardless of the priority setting above. The page lists two additional rules: Skip handling unit optimization, which is required if a pure FIFO strategy for automatic reservation is needed, and Use date instead of date time for FIFO consideration. For complete handling units, you can prioritize reserving complete handling units in bulk zones before reserving complete handling units in the picking zone.

The expiry rule and expired parts are separate on the page. Earliest Expiration Date is one of the priority rules, while the prerequisites list separately requires that the part must not be expired.

4.How do shipment-assigned quantities fit in?

The priority when reserving a customer order line is to first reserve the quantities assigned to the shipment lines, starting with the oldest shipment first, and then reserve the quantity that is not assigned to any shipment.

The reservation stores the shipment ID, either as the shipment ID of the shipment line reserved, or as zero (0) when a quantity not assigned to any shipment is reserved. The page also states an assumption: that the customer orders will be reserved in the same order as delivered. When the full or partial quantity does not get reserved, a shortage record is created for the part.

5.Do created transport tasks count as available stock?

Created transport tasks can be considered as available to reserve, depending on the configuration on the site. In the site you can configure whether you allow reserving from created transport tasks with destination move to inventory. When a reservation is made from a transport task, the system tries its best to keep the reserved material on the same transport task. Two-stage picking and pick by choice are covered in flexible reservations in IFS Cloud.

6.What overrides the rules?

Manual reservations by the user will always have priority over the set rules. The sentence is about the rule order: a manual choice beats the automatic rules.

The sentence does not make a manual reservation possible in every situation. The documentation states for the setting value Non-Manual Reservation that the parts in the location cannot be manually reserved except from the activities it lists. Warehouse and customer service therefore agree separately who reserves by hand and which locations are closed to it.

7.How does automatic reservation run, and what does the user see?

Automatic reservation starts a reservation job in the background. This means that the user does not receive an immediate response as to whether the reservation has succeeded or not. The user can follow up the order lines that did not get fully reserved in the Handle Customer Order Shortages page.

8.Which decisions belong to the warehouse owner and customer service?

Three decisions need a named owner. The warehouse owner decides the order of the rules, which rules are skipped and whether handling unit optimization is used. Warehouse and customer service decide who reserves manually. The warehouse decides whether created transport tasks may be reserved from. Putaway zones belong to the location model, described in warehouse structure design in IFS Cloud. Picking strategy configuration is covered in advanced picking strategies in IFS Cloud. Promising a date from the master schedule is a different mechanism, described in Master Scheduling Available to Promise.

9.How do you test the rules before go-live?

Test the rules with two candidate stock records that differ in one attribute, and write down the expected record before each run. Set the rule under test first in the order for that run.

Scenario Rule set Expected stock reserved Owner
Two locations differ in expiration date Earliest Expiration Date first The location with the earliest expiration date Warehouse lead
Two locations differ in receipt date Earliest Receipt Date first The location where the earliest receipts were performed Warehouse lead
Two handling units differ in number of parents Outermost Handling Unit first The handling unit with as few parents as possible Warehouse lead
Handling unit optimization on, rule order changed Any order Complete handling units first, regardless of the priority setting Warehouse lead
Order line with quantities on two shipments and an unassigned quantity Any order Quantities assigned to shipments first, starting with the oldest shipment, then the unassigned quantity; record the shipment ID or 0 on each reservation Customer service
User reserves a record the rules would not choose Any order The record the user chose; record whether Non-Manual Reservation blocks the attempt Customer service
Run automatic reservation on a short order line Any order No immediate response; the line appears on Handle Customer Order Shortages Customer service

10.What does a reservation rule checklist contain?

The reservation setup is ready for go-live when each check below has a record behind it.

  1. The order of the five priority rules is written down, with the rules that are skipped.
  2. Handling unit optimization is decided, and so are the two additional rules of the page.
  3. Whether created transport tasks may be reserved from is decided on the site.
  4. The people who reserve manually are named, and the locations with Non-Manual Reservation are listed.
  5. Someone reads Handle Customer Order Shortages after each reservation job.
  6. The seven test scenarios are recorded with evidence.

11.Frequently asked questions

How does IFS Cloud decide which stock to reserve automatically?

IFS Cloud automatic reservation can use five priority rules, depending on the setup on the site: Earliest Expiration Date, Earliest Receipt Date, Highest Putaway Zone Ranking, Largest Quantity on Handling Unit and Outermost Handling Unit. They apply when the prerequisites of automatic reservation are fulfilled.

Can the order of the reservation rules be changed?

The order of the IFS Cloud reservation priority rules can be defined, and some of the rules can be skipped if they are not considered important. The documentation places this in the setup on the site and does not state who sets it. With handling unit optimization, complete handling units are reserved first regardless of the priority setting.

Do manual reservations follow the rules?

Manual reservations by the user in IFS Cloud always have priority over the set reservation rules. The statement concerns the choice of stock, not the permission to reserve: for the setting value Non-Manual Reservation, the documentation states that parts in the location cannot be manually reserved except from the activities it lists.

Which shipment quantities are reserved first on a customer order line?

On an IFS Cloud customer order line, the quantities assigned to shipment lines are reserved first, starting with the oldest shipment, and then the quantity that is not assigned to any shipment. The reservation stores the shipment ID of the shipment line, or zero when the quantity is not assigned to a shipment.

Why does automatic reservation not show a result when it runs?

Automatic reservation in IFS Cloud starts a reservation job in the background, so the user does not receive an immediate response as to whether the reservation has succeeded. Order lines that did not get fully reserved are followed up on the Handle Customer Order Shortages page.

12.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Does the system reserve stock the warehouse does not want to ship first?

A review of the reservation rule order against the way your warehouse ships shows which rule picks the stock for each order line.

Book a reservation rule review Read about orders without coverage

Abstract illustration on a navy background with the article title: IFS Cloud Ship Goods and Assets: What It Creates

IFS Cloud Ship Goods and Assets: What It Creates

Details
Created: 29 October 2026
Last Updated: 07 November 2026
  • IFS Cloud
  • Delivery
  • Inventory
  • IFS Cloud Implementation
  • Distribution Orders

Independent IFS Cloud practice · Inventory transfer design

Know which documents the system creates before you start the move

The IFS Cloud Ship Goods and Assets activity starts one move, and the system creates different documents depending on who receives the goods. If the set-up behind each route is not known, a move fails for a missing default, or master data appears that nobody planned. The stock moves, and with it come documents, reservations and master data the business did not expect. This article follows the 26R1 page on shipping goods and assets and the 25R2 page on the shipment order.

Key takeaways

  • Depending on whether the receiver site is within the same company or a different company, a shipment order or a distribution order is used to administrate the move.
  • Within one company, a shipment order is created in either planned or released state, depending on the Create in Released Status option, and the selected parts or handling units are reserved against its lines.
  • Between companies, distribution orders are created per part and released, and one internal customer order and one internal purchase order are created and released.
  • Missing sales parts at the sender site and missing purchase parts at the receiving site are created automatically, including the supplier for the purchase part.
  • The inter-company scenario is not available for project inventory, configured parts or ownerships other than Company Owned, and the shipment order does not support goods movement between companies.
  • The two-route table sets out the condition, the documents created and the stated limits for each route.

1.What does the activity do, and how does it choose the route?

The activity initiates the move of an inventory part, a non inventory part, no part or a handling unit between a site and/or a remote warehouse, and it chooses the document by the company of the receiver. The page states that, depending on if the receiver site is within the same company or a different company, a shipment order or distribution order will be used to administrate the move.

The page positions the activity for goods that need transport outside the warehouse. A transport task is better suited to stock movement within the warehouse, as covered in warehouse tasks in IFS Cloud. The comparison of the shipment order and the distribution order as tools is in shipment order in IFS Cloud and distribution orders in IFS Cloud, and this article does not repeat it.

Receiver Documents created Stated limits
Site in the same company A shipment order, in planned or released state depending on the Create in Released Status option; selected parts or handling units reserved against its lines The shipment order does not handle consignment stock or supplier-owned parts
Site in a different company Distribution orders per part, released; one internal customer order and one internal purchase order, released; parts reserved to the corresponding customer order lines Not available for project inventory, configured parts or ownerships other than Company Owned

2.What happens inside one company?

Inside one company a new shipment order is created in either planned or released state, depending on the Create in Released Status option, and the selected parts or handling units are reserved against the shipment order lines. The page also says it is possible to add more parts and quantity to an existing shipment order with the same sender and receiver.

The quantity is consolidated into the shipment order line based on part, condition code, configuration ID, ownership, owner, demand code and reference, and project activity. The page’s example: if moving ten serials, it will be one shipment order line with the quantity 10 PCS. The ownership key links the move to part ownership in IFS Cloud, and the shipment documents to consolidated shipment in IFS Cloud.

Prerequisites sit on both the data and the stock. To ship using a shipment order (intra company), the page says the following basic data should be set up as shipment order default values: Requisitioner, Ship Via, Delivery Terms and Shipment Types. For stock, the available quantity of the part should be greater than zero, and for a handling unit the entire quantities of the parts must be available. A part received into an arrival or quality assurance location can be shipped too, with the purchase order receipt added as demand code and reference on the shipment order line, but from these locations it is only possible to move goods to a receiver in the same site.

3.What happens between companies?

Between companies the activity works through distribution orders and internal orders. Distribution orders will be created per part and released. One internal customer order and one internal purchase order will be created and released, and the parts will be reserved to the corresponding customer order lines.

The prerequisites differ from the intra-company route. The page states that an internal customer and supplier need to be configured and connected to the respective site, and that if a sales part or the supplier for a purchase part is missing, the inventory part must have a Unit Cost. The price set is fetched from the inventory part cost. The decision about who maintains the internal customer and supplier records is a master data decision, not a warehouse one. The sites involved are covered in site cluster functionality.

4.What does the system create automatically?

If sales parts are missing in the sender site and/or purchase parts are missing in the receiving site, they will be created automatically, including the supplier for the purchase part. These are master data records that the business did not enter itself.

Treat this as a decision and not as a convenience. Decide who approves the automatically created parts, how they are named and whether the unit cost on the inventory part is the cost the receiving company should see.

5.What are the limits?

The inter company scenario is not available for project inventory, configured parts or ownerships other than Company Owned. The shipment order page adds that the shipment order doesn’t support goods movement between companies, and that for now it doesn’t handle consignment stock or supplier owned parts.

A distribution order and inter-site order concept cannot handle goods movement when remote warehouses are involved, according to the shipment order page. The remote warehouse side is covered in the IFS Cloud remote warehouse article. Stock that falls under one of the stated limits needs another route, which has to be agreed before the first move.

6.Which decisions belong to inventory, finance and master data owners?

Inventory owns the shipment order defaults and the Create in Released Status option for the intra-company route. Master data owners own the internal customer and supplier, the sales parts and purchase parts, and the unit costs. Finance owns the intercompany treatment of the documents that the inter-company route creates, and decides how the price from the inventory part cost is handled between the companies.

7.How do you test both routes before go-live?

Test each route with one move and write down the documents you expect before it runs.

Move Expected documents Owner
Within one company, defaults set A shipment order in the state set by the Create in Released Status option; stock reserved against its lines Inventory lead
Within one company, a default missing Record what the activity does when Requisitioner, Ship Via, Delivery Terms or Shipment Types is not set up Inventory lead
Between companies, parts exist Distribution orders per part, one internal customer order and one internal purchase order, all released; stock reserved to the customer order lines Inventory lead and finance
Between companies, parts missing Sales parts and purchase parts created automatically, including the supplier Master data owner
Between companies, stock under a limit Project inventory, configured part or non-company ownership: the scenario is not available Inventory lead

8.What does a transfer set-up checklist contain?

The transfer set-up is ready for go-live when each of the checks below has a record behind it.

  1. The shipment order defaults Requisitioner, Ship Via, Delivery Terms and Shipment Types are set up.
  2. The Create in Released Status option is decided.
  3. The internal customer and supplier are configured and connected to the respective sites.
  4. The unit cost is set on inventory parts where sales parts or purchase parts may be created automatically.
  5. Someone approves automatically created master data.
  6. Stock that falls under the inter-company limits has an agreed alternative route.
  7. The five test moves are recorded with evidence.

9.Frequently asked questions

What does the Ship Goods and Assets activity do in IFS Cloud?

The Ship Goods and Assets activity in IFS Cloud initiates the move of an inventory part, a non inventory part, no part or a handling unit between a site and/or a remote warehouse. Depending on whether the receiver site is within the same company or a different company, a shipment order or a distribution order is used to administrate the move.

Which document is created for a move within one company?

A shipment order is created, in either planned or released state depending on the Create in Released Status option. The selected parts or handling units are reserved against the shipment order lines. The shipment order defaults Requisitioner, Ship Via, Delivery Terms and Shipment Types should be set up first.

Which documents are created for a move between companies?

Distribution orders are created per part and released. One internal customer order and one internal purchase order are created and released, and the parts are reserved to the corresponding customer order lines. An internal customer and supplier need to be configured and connected to the respective site.

Can the inter-company route move stock that is not company owned?

No. The IFS Cloud documentation states that the inter company scenario is not available for project inventory, configured parts or ownerships other than Company Owned. The shipment order also does not support goods movement between companies.

What happens when sales parts or purchase parts are missing for an inter-company move?

If sales parts are missing in the sender site and/or purchase parts are missing in the receiving site, IFS Cloud creates them automatically, including the supplier for the purchase part. When a sales part or the supplier for a purchase part is missing, the inventory part must have a Unit Cost.

10.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Do transfers between your companies create things you did not set up?

A review of the transfer set-up for both routes, with test moves, shows which defaults and master data each route needs. Inventory, finance and master data owners take part.

Book a transfer set-up review Read about remote warehouses

Abstract illustration on a navy background with the article title: IFS Cloud Part Availability Control: What Each Setting Does

IFS Cloud Part Availability Control: What Each Setting Does

Details
Created: 28 October 2026
Last Updated: 07 November 2026
  • IFS Cloud
  • Warehousing
  • Inventory
  • IFS Cloud Implementation
  • Best Practices

Independent IFS Cloud practice · Inventory settings design

Know which function reads which parameter before you change an availability control

An IFS Cloud part availability control is a small record whose parameters act on different functions at once: planning, reservation, issue, movement, scrapping, counting and refill. If the parameters are set without knowing which function reads which, stock is available to a function that should not see it, or blocked from one that needs it. Planning then counts stock that the floor cannot use, or the reverse. This article follows the 25R2 page on entering an availability control ID and the page on reservation management.

Key takeaways

  • Availability control records can be linked to inventory stock records or be set as a default part availability control on the Warehouse Navigator page, and they are used for determining the availability when reservations are made on inventory part locations.
  • The nettable parameter governs availability and planning. Parts on a quality assurance or arrival location are still seen as supply and are not affected by it.
  • The automatic reservation parameter does not block manual reservation. A separate parameter, Part Manual Reservation Control, can block it with the setting Non-Manual Reservation.
  • The only possible way to make a non-order issue is to issue inventory parts using the Issue Inventory Part page.
  • Movement set to Not Allowed stops parts from moving to any location unless the availability is changed, including moves from a quality assurance or arrival location in a purchase receipt.
  • The parameter table lists nine parameters with the function each one governs, and the test table tries each on one stock record.

1.What is a part availability control, and where is it attached?

A part availability control is a record that is used for determining the availability when you make reservations on inventory part locations. It can be linked to inventory stock records or be set as a default part availability control on the Warehouse Navigator page. The availability control ID and settings can be linked to a specific inventory stock record to control the use of that specific stock record.

A warehouse default and a control on a stock record are therefore two places to look when stock behaves unexpectedly. The warehouse default for a remote store is covered in the IFS Cloud remote warehouse article, and the location model in warehouse structure design.

2.Which parameters does the control hold, and what does each govern?

The control holds nine parameters that the pages describe, each acting on a different function. The table summarises what the pages state, and the sections below give the detail.

Parameter Function it governs
Nettable (Part Supply Control) Whether the part on the location is available and can be planned
Automatic reservation Whether automatic reservations can be made
Part Manual Reservation Control Whether the parts in the location can be manually reserved
Order issue Which parts automatic order issues cover
Non-order issue Which parts non-order issues can be made for
Movement Whether parts can be moved to any location
Scrap control Whether inventory parts can be scrapped manually from stock
Counting control Whether you can enter a quantity-counted value other than the quantity on hand
Putaway Zone Refill Source Whether a stock record with a control is considered a source in the refill process

3.What does the nettable parameter govern, and what does it not?

The nettable parameter means that the part on the location is available and can be planned. Parts on a quality assurance or arrival location are still seen as supply and are not affected by the nettable parameter. Some location types, such as shipment and arrival, are not available for reservation.

For a remote warehouse the page on remote warehouses adds a case: if the setting is Not Nettable, the parts are not plannable or available in the availability check, order proposal and MRP, but on the remote warehouse Parts tab they are considered plannable. Order promising is covered in high-fidelity discrete order promising.

4.How do the reservation parameters work?

Automatic reservations can be made for parts without availability control IDs and for parts with the automatic reservation parameter set to Allowed. The page continues that manual reservations can always be made, regardless of the setting of that parameter. The sentence is about the automatic reservation parameter only: that parameter does not block manual reservation.

Manual reservation has its own parameter. On the remote warehouse page, Part Manual Reservation Control with the setting Non-Manual Reservation means that the parts in the location cannot be manually reserved, except from the activities done by a user who has the specific remote warehouse set as the default or connected warehouse. A manual reservation can therefore be blocked, by a different parameter from the one the availability control page describes.

Automatic reservation has further conditions. The Reservation Management page states that the inventory part might be connected to a part availability control ID, and if so, the availability control shall allow reservations. It adds that the inventory location must be a picking location, that it cannot be a floor stock, a manufacturing cell, an inspection location or a shipment inventory, and that the part must not be expired. Sales order lines without coverage are covered in sales orders without coverage and flexible reservations.

5.What do the issue parameters govern?

Two parameters govern issue, one for order issue and one for non-order issue. Automatic order issues cover parts with availability control IDs that have the part order issue control set to Order Issue, and parts without availability control IDs. The non-order issue parameter allows non-order issues for parts depending on two conditions: parts with availability control IDs that have the part non-order issue control set to Non-Order Issue, and parts without availability control IDs.

The page states that the only possible way to make a non-order issue is to issue inventory parts using the Issue Inventory Part page. A control set to Non-Order Issue therefore does not open any other route.

6.What do movement, scrap, counting and refill source govern?

Movement is the parameter that can stop stock from leaving a location. If it is set to Not Allowed, the movement of parts is restricted and the parts cannot be moved to any location unless the availability is changed. This also applies to movements of parts to inventory from a quality assurance or arrival location in a purchase receipt.

The scrap control parameter specifies whether the inventory parts can be scrapped manually from stock, and that includes scrapping performed on a quality assurance or arrival location upon inspection. The counting control parameter specifies whether you can enter a quantity-counted value other than the quantity on hand value. The Putaway Zone Refill Source option must be selected if a stock record with a part availability control should be considered as a source in the refill process.

Kits use the control as well: kit statuses can be linked to part availability control IDs, as covered in kits and kit assembly orders in IFS Cloud.

7.Which decisions belong to inventory and planning together?

Inventory and planning decide together which locations restrict which functions, and who may change a control. Planning cares about the nettable parameter, the floor about reservation, issue and movement. A control changed by one side for its own reason affects the other side’s function. Name one owner for each control, write down the purpose of each restriction, and review the controls when a location changes use.

8.How do you test an availability control?

Test a control with one stock record per setting, try the function the setting governs, and write down the expected result first.

Stock record setting Function tried Expected result Owner
Not Nettable Availability check and planning Not available or plannable, except as the page states for quality assurance, arrival and remote warehouse Parts tab Planner
Automatic reservation not allowed Automatic reservation, then a manual reservation No automatic reservation; the manual reservation is not blocked by this parameter Warehouse lead
Non-Manual Reservation Manual reservation Blocked, except for the activities the page names Warehouse lead
Non-Order Issue Issue through the Issue Inventory Part page The non-order issue can be made Warehouse lead
Movement Not Allowed Move to another location; move from arrival in a purchase receipt Both are blocked unless the availability is changed Inventory lead
Scrap and counting control Manual scrap; count with a different quantity than on hand Each follows its parameter Inventory lead
Putaway Zone Refill Source Refill run The record counts as a source only if the option is selected Planner

9.What does an availability control checklist contain?

Availability controls are ready for go-live when each of the checks below has a record behind it.

  1. Each control has an owner and a written purpose.
  2. The warehouse defaults and the controls on stock records are both reviewed.
  3. Automatic reservation and Part Manual Reservation Control are decided separately.
  4. Users know that a non-order issue is made only through the Issue Inventory Part page.
  5. Movement Not Allowed is used only where a block on purchase receipt moves is intended.
  6. Scrap control, counting control and refill source are decided per location type.
  7. The seven test cases are recorded with evidence.

10.Frequently asked questions

What is a part availability control in IFS Cloud?

A part availability control in IFS Cloud is a record used for determining the availability when you make reservations on inventory part locations. It can be linked to inventory stock records or be set as a default part availability control on the Warehouse Navigator page. Its parameters govern planning, reservation, issue, movement, scrapping, counting and refill.

What does the nettable parameter do?

The nettable parameter in IFS Cloud means that the part on the location is available and can be planned. Parts on a quality assurance or arrival location are still seen as supply and are not affected by it.

Can I still reserve manually when automatic reservation is not allowed?

Yes, as far as the automatic reservation parameter is concerned: the IFS Cloud documentation says manual reservations can always be made regardless of the setting of that parameter. A separate parameter, Part Manual Reservation Control, can block manual reservation when it is set to Non-Manual Reservation, so check that parameter as well.

How do I make a non-order issue?

The only possible way to make a non-order issue in IFS Cloud is to issue inventory parts using the Issue Inventory Part page. The non-order issue parameter allows it for parts with a control set to Non-Order Issue and for parts without an availability control ID.

Where is the default availability control for a warehouse set?

A default part availability control for a warehouse in IFS Cloud is set on the Warehouse Navigator page. For a remote warehouse the documentation describes entering a Default Part Availability Control on the General tab. Individual stock records can carry their own control, and some settings can be overridden there.

11.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Does stock show as available and still cannot be reserved?

A review of availability controls against the way each location is used shows which parameter blocks which function. Inventory and planning take part.

Book an availability control review Read about remote warehouse defaults

Abstract illustration on a navy background with the article title: IFS Cloud Remote Warehouse: Defaults, Refill, Arrival

IFS Cloud Remote Warehouse: Defaults, Refill, Arrival

Details
Created: 28 October 2026
Last Updated: 07 November 2026
  • IFS Cloud
  • Warehousing
  • Inventory
  • IFS Cloud Implementation
  • Best Practices

Independent IFS Cloud practice · Warehouse set-up design

Decide what remote stock may do before the first part moves out

An IFS Cloud remote warehouse holds stock away from the main warehouse, for example at a supplier or in a service van, and it is still stock. If its availability, movement and refill settings stay at the ordinary defaults, the remote stock can be reserved, issued or used to refill other locations in ways the business did not intend. This article follows the documentation page on remote warehouses in the 26R1 tree; the 25R2 copy carries the same text.

Key takeaways

  • A default part availability control can be entered at warehouse level to limit the stock in a remote warehouse for functions such as reserve and issue; some settings can be overridden on stock records.
  • The page gives six values as one suggested remote warehouse setup, which can be adjusted to the business requirements. They are suggestions and not requirements.
  • Part Movement Control should be All Allowed so that parts can be moved with a transport task, and Putaway Zone Refill Source should be disabled so that remote stock does not refill other locations.
  • The Refill Parts command creates transport tasks, shipment orders or purchase requisitions to reach the refill level, and it has prerequisites on the part, the assortment and the ranking of the warehouse.
  • Arrival defaults are used when registering arrival of goods in the remote warehouse.
  • Distribution orders cannot handle goods movement when remote warehouses are involved; a shipment order can.

1.What is a remote warehouse in IFS Cloud, and how does it differ from an ordinary warehouse?

A remote warehouse in IFS Cloud is a stock location with its own defaults for availability, refill and arrival, and it takes part in internal goods movement within one company. The location structure of an ordinary warehouse is covered in warehouse structure design in IFS Cloud, and this article does not repeat it.

The page also describes two address uses. A delivery address can be defined per remote warehouse, and the address type Supplier can be used when you have defined a remote warehouse at a supplier for purchase orders with outsourcing.

2.How do default availability controls limit remote stock?

To limit the stock in a remote warehouse for other functions like reserve and issue, a default part availability control can be entered on warehouse level. It will be possible to override some of the part availability control settings on stock records. The page on entering an availability control ID adds that availability control records can be linked to inventory stock records or be set as a default part availability control on the Warehouse Navigator page, and that they are used for determining the availability when you make reservations on inventory part locations.

The warehouse default therefore sets the starting point for every stock record in the remote warehouse, and a stock record can differ from it for the settings that may be overridden. Decide who may override a setting on a stock record.

3.Which values does the documentation suggest, and why?

The page calls the following values one suggested remote warehouse setup and states that it is possible to make adjustments depending on the business requirements. They are entered as a Default Part Availability Control on the Warehouse Navigator/General tab.

Setting Suggested value What the page says
Part Supply Control Not Nettable Not Nettable parts are not plannable or available in the availability check, order proposal and MRP, but on the remote warehouse Parts tab they are considered plannable
Part Auto Reservation Control Non-Automatic Reservation Exceptions exist for activities done by a user who has the remote warehouse as the default warehouse
Part Manual Reservation Control Non-Manual Reservation The same exceptions apply
Part Order Issue Control Non-Order Issue The same exceptions apply
Part Movement Control All Allowed It should be set to All Allowed to be able to move the parts with a transport task
Putaway Zone Refill Source Disabled It should be disabled to avoid remote warehouse stock being used to refill other locations

The activities named in the exceptions are Work Task, Prepare Work Order, Report In Work Order and Maintenance Material Requisition. The page adds that the Part Non-Order Issue Control, Part Scrap Control and Part Counting Control can have any setting. For reservation by users, it states that if the logged-in user has connected warehouses but none of them is the default, no reservation will be done.

Moving parts that have a different availability control needs one more setting: Allow Deviating Part Availability Control has to be enabled to make it possible to move parts with deviating part availability control using a transport task. Transport tasks and their planning are covered in warehouse tasks in IFS Cloud.

4.How does refill work?

The Refill Parts command creates transport tasks, shipment orders or purchase requisitions to reach the refill level. The page lists prerequisites for it and for the Refill All Putaway Zones job, and its suggested set-up adds two settings that refill depends on:

  • The inventory part on the connected remote warehouse assortment has the setting Refill Putaway Zones (Inventory Part/Main tab) set to either From Putaway Zones or From All Stock Locations.
  • The remote warehouse is the highest ranked putaway zone with available capacity, with regard to the refill point quantity, receipt control, capacities and conditions and the capabilities of the warehouse.
  • Appear as Putaway Zone is enabled, which makes it possible to run manual or scheduled refill, and the warehouse should be the highest ranking to make sure that parts are refilled in it.
  • At site level, Refill Putaway Zones is set to From All Stock Locations, a setting that is needed to enable the refill jobs and that can be overridden on the inventory part.

If a part exists on two or more connected assortments, the one with the highest priority is made active for the remote warehouse. The Refill All Putaway Zones job can be used to perform a refill directly or to schedule it, regardless of the Automatically Refill Putaway Zones setting. For a moving warehouse such as a service van, the page says the Automatically Refill Putaway Zones setting shall be disabled, to avoid a transport task reserving material that cannot be physically moved to the destination.

Two further settings shape the flow. To prevent putaways from being done directly to the remote warehouse, the Putaway Destination setting should be disabled. And if a drop-off location exists between the from and the to location, the system automatically creates a two-step transport task. Storage Optimization removes excess from the selected remote warehouse where the part has the Remove Excess option enabled and the quantity on hand is greater than the refill-to quantity.

5.What happens at arrival?

Arrival Defaults are used when registering arrival of goods in the remote warehouse. This article does not describe what the arrival defaults contain; read them in your release, decide them with the warehouse owner and test them. The scanning of such arrivals on the floor is covered in warehouse data collection in IFS Cloud.

6.How does stock move between sites and remote warehouses?

A shipment order handles internal goods movement between sites and remote warehouses in the same company. The page on the shipment order lists four routes: from site to site, from site to remote warehouse, from remote warehouse to site and from remote warehouse to remote warehouse.

The same page states that a distribution order and inter-site order concept cannot handle goods movement when remote warehouses are involved. The flow is described in shipment order in IFS Cloud and, for the distribution order, in distribution orders in IFS Cloud. The shipment documents are covered in consolidated shipment in IFS Cloud, and the ownership of moved stock in part ownership in IFS Cloud.

7.Which decisions belong to the warehouse owner and planning?

The warehouse owner decides the availability control of the remote store, the refill level and who may issue from it. Planning decides whether the remote stock counts as plannable, which the Not Nettable value and the Parts tab handle in a particular way. Each of the six suggested values is a decision to adopt or to adjust, and the record should say which.

8.How do you test a remote warehouse before go-live?

Test a remote warehouse with one scenario per behaviour the page describes, and write down the expected result before each test.

Scenario Expected result Owner
Reserve remote stock with the suggested control Reservation follows the control; check the exceptions for users with the remote warehouse as default Planner
Issue remote stock to an order Non-Order Issue applies as set; record any difference Warehouse lead
Move parts with a transport task Possible with Part Movement Control All Allowed Warehouse lead
Run Refill Parts Transport tasks, shipment orders or purchase requisitions created to reach the refill level Planner
Register arrival of goods The arrival defaults of the remote warehouse are used Receiving clerk
Move goods by shipment order Route from site to remote warehouse and back works; a distribution order is not used for it Warehouse lead

9.What does a remote warehouse set-up checklist contain?

A remote warehouse is ready for go-live when each of the checks below has a record behind it.

  1. A default part availability control is entered on the warehouse, and each of the six suggested values is adopted or adjusted by decision.
  2. It is clear who may override settings on stock records.
  3. Part Movement Control allows transport tasks to move the parts.
  4. The refill prerequisites are checked: part setting, assortment, ranking and site setting.
  5. Putaway Destination and Automatically Refill Putaway Zones are set to match how the store is used.
  6. The arrival defaults are decided.
  7. Stock is moved by shipment order, not by distribution order.
  8. The six test scenarios are recorded with evidence.

10.Frequently asked questions

What is a remote warehouse in IFS Cloud?

A remote warehouse in IFS Cloud is a warehouse with its own defaults for part availability control, refill and arrival, taking part in internal goods movement within one company. A shipment order can move goods between sites and remote warehouses, while a distribution order cannot handle goods movement when remote warehouses are involved.

How do I stop remote warehouse stock from being reserved or issued by default?

Enter a default part availability control on the remote warehouse in IFS Cloud. The documentation suggests Non-Automatic Reservation, Non-Manual Reservation and Non-Order Issue as part of one suggested setup, which can be adjusted to the business requirements. Some settings can be overridden on stock records.

Why can remote warehouse stock not be moved with a transport task?

Check Part Movement Control first. The IFS Cloud documentation says it should be set to All Allowed to be able to move the parts with a transport task. For parts with a deviating part availability control, the Allow Deviating Part Availability Control setting has to be enabled.

What does the refill command create?

The Refill Parts command in IFS Cloud creates transport tasks, shipment orders or purchase requisitions to reach the refill level. It requires that the inventory part on the connected assortment has Refill Putaway Zones set to From Putaway Zones or From All Stock Locations, and that the remote warehouse is the highest ranked putaway zone with available capacity.

How is stock moved between a site and a remote warehouse?

Stock is moved by shipment order in IFS Cloud. The documentation lists routes from site to site, site to remote warehouse, remote warehouse to site and remote warehouse to remote warehouse, within one company. The distribution order and inter-site order concept cannot handle goods movement when remote warehouses are involved.

11.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Does the system treat your remote stores like any other stock?

A review of the remote warehouse set-up against the way the stores are used shows which settings were left at their defaults. The warehouse owner and a planner take part.

Book a remote warehouse review Read about warehouse structure design

Abstract illustration on a navy background with the article title: IFS Cloud Kits and Kit Assembly Orders: How They Work

IFS Cloud Kits and Kit Assembly Orders: How They Work

Details
Created: 28 October 2026
Last Updated: 07 November 2026
  • IFS Cloud
  • Inventory
  • Planning
  • IFS Cloud Implementation
  • Best Practices

Independent IFS Cloud practice · Inventory design

Set up the kit master part correctly, and know what planning leaves to you

An IFS Cloud kit assembly order builds or changes a kit serial, which is one stocked unit made of components. Inventory, assembly and planning all touch the kit. If the master part is set up wrongly, or planning is assumed to cover the components, the kit is built from stock nobody planned. This article follows the 26R1 documentation on kits and on the kit assembly order.

Key takeaways

  • A kit is a pre-defined collection of parts managed as a single unit. It can be purchased or assembled in-house through a kit assembly order.
  • A package part on a customer order is a separate sales mechanism and not an inventory kit.
  • The kit master part must be serial-tracked, must have no existing part serial records and must not be configurable, and it should not be Catch UoM enabled.
  • The kit definition is a global template valid across all sites, and it can be modified only when no kit assembly order is in progress for the kit part.
  • Receiving the kit assembly order closes it; there is no Close command.
  • MRP cannot create kit assembly orders for shortages and cannot plan the components of existing ones, so planning for kits is limited to the parent kit part through Purchasing.

1.What is a kit in IFS Cloud?

A kit is a pre-defined collection of individual parts or components that are grouped together and managed as a single unit. The page states that kits can be purchased from vendors or assembled in-house via a kit assembly order.

A kit in this sense is not a package part. A package part is one of three sales part types, supplied on the customer order line with the supply code Pkg, Internal Purchase Direct or Purchase Order Direct, and the sales pages call it a kit informally. The inventory kit is a serial-tracked master part with the Kit Part toggle, a global kit definition and kit assembly orders. The Kits and Kit Assembly Order pages never mention package parts, so this article does not cover how a package part is sold. Configure-to-order is another mechanism again, covered in configure-to-order purchasing.

2.What must the kit master part look like?

The page sets conditions on the kit master part, and the wording of each condition carries its strength. The table keeps the page’s modal verbs.

Condition Wording on the page
Serial tracking The part must be set up as serial-tracked in inventory
Existing serial records There must be no existing Part Serial records for the part
Configurable The part must not be Configurable
Catch UoM The part should not be Catch UoM enabled
Cost level, if inventory part records exist The Part Cost Level must be set to Cost per Serial
Zero cost, if inventory part records exist The Zero Cost setting must be configured as Zero Cost Allowed

Components have their own limit: parts that are Configurable or Catch UoM enabled cannot be added as kit components in a kit definition. The serial tracking decision for the master part is covered in lot and serial tracking decisions in IFS Cloud, and cost levels in inventory valuation methods and cost levels.

3.What does the kit definition hold, and how far does it reach?

The kit definition serves as the global template for the kit part and is valid across all sites. Each component part may be either tracked or non-tracked, and a Quantity per Assembly value specifies how many units of each component are required to assemble one kit part.

The definition can be modified when required, given that no kit assembly orders are in progress for the kit part. The page on creating a kit assembly order repeats the limit: it is not possible to update the kit definition if the kit assembly order is in In Progress state. A change to a kit therefore has to be planned around the orders in progress, and one person should own the definition.

4.Which kit statuses exist and what do they mean?

A kit has one of four statuses: Empty, Incomplete, Complete or Overcomplete. Empty means that no components exist in the kit, and the page defines each of the other three. Kit statuses can be linked to Part Availability Control IDs.

Whether to link statuses to availability controls is a decision for inventory and sales together, and the link should be tested before it is relied on. The page on Kit Serial Components displays the current contents of a kit serial regardless of whether it is in inventory, in transit, issued or in any other position.

5.How does a kit assembly order work?

A kit assembly order is used to modify an existing kit serial or to create a new one, and it can be created from the Inventory Parts In Stock page or from the Kit Assembly Order page. From a stock record, the stock record should be for a kit part, the available quantity should be greater than 0 and the ownership should be Company Owned. The ownership types are covered in part ownership in IFS Cloud.

The two pages state the prerequisites in different words. The kit assembly order page says the kit part should exist as an Inventory Part, and the create page says it should exist in the Master Part, with a kit definition for the kit part. Check both in your release.

Saving the header does two things. It automatically populates the kit components based on the kit definition in the Required Content tab, and because the kit part is issued from stock when the header is created, any existing validation for issuing an inventory part, such as part availability control, should fire, as the page puts it. Both standard component parts and alternate component parts are shown in one list. The kit expiration date defaults to the earliest expiration date among the components and can be overridden manually.

6.Which statuses does a kit assembly order pass through?

A kit assembly order is Planned as soon as a header is created for a new kit part. An issue transaction triggers the In Progress state, and receiving the kit assembly order moves it to Closed; there is no Close command. A kit assembly order created for an existing kit serial, for example from Inventory Parts In Stock, starts In Progress.

Two more rules limit what a planner can undo. The header can be deleted when it is in Planned status, and cancelling can be done when the order is In Progress. Planned orders for new kit serials can be created ahead as a manual planning aid and then processed by warehouse staff.

7.What do kit assembly orders post?

The cost of the kit part is transferred to the WIP account, posting type M311, by creating the transaction KAOKSISS. The page also names a receipt transaction, KAOKSREC, and a cost difference transaction, KAODIFF+, and states that an existing company needs its posting set-up updated from the STD company template to work with the newly introduced posting types M311 and M312.

That last statement is a go-live task for finance and not an option. Finance decides the accounting treatment, and how events turn into ledger entries is covered in posting control in IFS Cloud.

8.What does MRP plan, and what not?

MRP plans the kit part and not the assembly. The page states that MRP cannot create kit assembly orders for shortages, nor can it plan component parts for existing kit assembly orders, which means planning for kits is limited to the parent kit parts through Purchasing. Kit parts, like standard inventory parts, can be planned for demand using MRP, and when shortages occur MRP can generate purchase requisitions as supply orders.

The consequence is that component availability for a kit assembly order needs a person. Decide who checks components before an order is created. MRP itself is covered in dynamic structures in MRP.

9.Which decisions belong to inventory, planning and sales?

Three questions need an owner before kits go live. Inventory decides which parts are kits and owns the kit definition. Planning decides who checks component availability, since MRP does not plan the components of an assembly order. Sales decides whether kits are sold as inventory kits or as package parts, which are separate mechanisms with separate set-up.

10.How do you test a kit before go-live?

Test a kit through its whole life, from definition to receipt, and write down the expected result before each step.

Step Expected result Owner
Define the kit The master part meets the conditions; the definition lists components and quantity per assembly Inventory lead
Create an assembly order from stock Header saved; Required Content filled from the definition; the kit part issued and availability control validated Warehouse lead
Issue components The order moves to In Progress Warehouse lead
Change the definition during an open order Not possible while the order is In Progress Inventory lead
Receive the kit The order moves to Closed; finance compares the postings, including those with posting types M311 and M312, with its expectation Warehouse lead and finance
Run MRP with kit demand Purchase requisitions for the kit part; no assembly order and no component planning Planner

11.What does a kit set-up checklist contain?

A kit set-up is ready for go-live when each of the checks below has a record behind it.

  1. Every kit master part meets the must and must-not conditions of the page.
  2. Cost per Serial and Zero Cost Allowed are set where inventory part records exist.
  3. No configurable or Catch UoM part is used as a component.
  4. One person owns each kit definition.
  5. The posting set-up includes M311 and M312.
  6. Someone checks component availability before assembly orders are created.
  7. The six test steps are recorded with evidence.

12.Frequently asked questions

What is a kit in IFS Cloud?

A kit in IFS Cloud is a pre-defined collection of individual parts or components that are grouped together and managed as a single unit. Kits can be purchased from vendors or assembled in-house through a kit assembly order. A kit is not the same as a package part on a customer order, which is a separate sales mechanism.

What conditions must a kit master part meet?

The IFS Cloud documentation says the kit master part must be set up as serial-tracked, there must be no existing part serial records, and the part must not be configurable. It adds that the part should not be Catch UoM enabled. Where inventory part records exist, the part cost level must be Cost per Serial and Zero Cost Allowed must be configured.

How do I create a kit assembly order?

A kit assembly order in IFS Cloud can be created from the Inventory Parts In Stock page or from the Kit Assembly Order page. From a stock record, the record should be for a kit part, the available quantity should be greater than 0 and the ownership should be Company Owned. Saving the header populates the kit components from the kit definition in the Required Content tab.

Does MRP plan the components of a kit assembly order?

No. The IFS Cloud documentation states that MRP cannot create kit assembly orders for shortages and cannot plan component parts for existing kit assembly orders. Planning for kits is limited to the parent kit part through Purchasing, where MRP can generate purchase requisitions for the kit part.

Can the kit definition be changed while assembly orders are in progress?

No. The IFS Cloud kit definition can be modified when required, given that no kit assembly orders are in progress for the kit part. The page on creating a kit assembly order states that it is not possible to update the kit definition while the order is In Progress.

13.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Can you say which kits are complete?

A review of kit definitions and the assembly process against the way kits are sold and built shows which master parts break the page’s conditions and where planning leaves a gap. Inventory, planning and finance take part.

Book a kit set-up review Read about serial tracking decisions

  1. IFS Cloud Warehouse Tasks: Priority and Planning
  2. IFS Cloud Part Ownership: Consignment and Loaned Stock
  3. IFS Cloud Outside Operations: Subcontracting Explained
  4. IFS Cloud Lot and Serial Tracking: Track Only What You Use

Page 1 of 3

  • 1
  • 2
  • 3