Skip to main contentSkip to footer

IFS Cloud Implementation Rescue: Diagnose, Decide, Recover

IFS Cloud implementation rescue for stalled projects: a diagnostic, a keep, repair or rebuild decision per area, and a dated recovery plan.

IFS Cloud implementation rescue · Independent IFS Cloud practice A stalled IFS Cloud project needs a diagnosis, a decision per area and dated gates The go-live…

Read more

IFS Cloud Reporting Tools: Quick Reports to Lobbies

IFS Cloud reporting tools in six layers: Quick Reports, Business Reporter, Lobbies, Power BI, Analysis Models and OData, and when to use each.

Independent IFS Cloud practice · Reporting From the weekly Excel export to a Lobby your team opens first Key takeaways IFS Cloud reporting tools fall into six…

Read more

Purchase Order Received but Not Closed in IFS Cloud

A purchase order line received in full can stay open in IFS Cloud. It lingers on open-PO reports and clutters them until someone closes it.

Independent IFS Cloud practice · Procurement The purchase order you received, and the line that never closed The goods arrived, the receipt matched, and every…

Read more

Purchase Order Short Receipt Left Open in IFS Cloud

Part of a purchase order arrives and the line stays open in IFS Cloud. An open remainder can keep counting as supply that is not coming.

Independent IFS Cloud practice · Procurement The purchase order that arrived half full and stayed open You ordered a hundred. Sixty arrived, the receipt was…

Read more

Purchase Order Over-Receipt in IFS Cloud

Goods can arrive in excess of the purchase order in IFS Cloud and pass inside a wide tolerance. How to list over-receipts before you pay for them.

Independent IFS Cloud practice · Procurement The delivery that brought more than you ordered, and nobody stopped it You ordered a hundred. A hundred and twenty…

Read more

Purchase Orders Priced Off Contract in IFS Cloud

A purchase order can be placed at a price the active agreement never authorised. The gap may surface only on the invoice. How to list it in IFS Cloud.

Independent IFS Cloud practice · Procurement The price you negotiated, and the order that ignored it There is an active blanket agreement on the part. Someone…

Read more

Purchase Order Currency Mismatch in IFS Cloud

A purchase order can carry a currency or rate that differs from the supplier default, so landed cost is off in IFS Cloud before the goods arrive.

Independent IFS Cloud practice · Procurement The order looked right in one currency, and cost the wrong number in another A purchase order in IFS Cloud carries…

Read more

Purchase Order Confirmation Mismatch in IFS Cloud

A supplier can confirm a purchase order at another quantity, price or date and the line still reads confirmed. How to list those gaps in IFS Cloud.

Independent IFS Cloud practice · Procurement The order you placed, and the confirmation that quietly changed it You raise a purchase order for a batch of…

Read more

Open Backorders After a Partial Delivery in IFS Cloud

A partial delivery ships and the rest is backordered in IFS Cloud. The open line can age with no new promised date until the customer asks.

Independent IFS Cloud practice · Sales The half that shipped, and the half nobody chased A customer orders ten and six are in stock, so six go out. The order…

Read more
Abstract illustration on a navy background with the article title: “One departure, several shipments, one setup”

IFS Cloud logistics · Shipment · Consolidated Shipment · Handling Units

Group order lines into one shipment per address, then send several shipments out as one departure

IFS Cloud consolidates outbound goods on two levels. A shipment collects order lines for one receiver address, and a consolidated shipment in IFS Cloud groups several shipments that leave the same site together, even when they go to different addresses. The shipment type decides how much of this happens automatically.

Key takeaways

  • A shipment in IFS Cloud goes to exactly one receiver address. Orders for different customers on the same truck belong in a consolidated shipment, which sits one level above the shipment.
  • The shipment type controls the flow: when shipments are created (at order release, at pick list creation or not automatically), which events run without a user, and which consolidation parameters decide whether an order line joins an existing shipment.
  • Consolidation parameters only apply to automatic connection. A user who connects an order line manually can put it into any open shipment.
  • Automatic connection of shipments to a consolidated shipment is a separate toggle on the shipment type, and it is disabled by default.
  • Handling units are optional, but without them IFS Cloud cannot calculate the weight and volume of each pallet or box, and the Packing Proposal has nothing to pack into.

Consolidation in IFS Cloud is decided by the shipment type, the handling unit data and the connect rules of the consolidated shipment, and those three are what this page explains. The forwarder and freight payer side is covered in Consolidated Shipment in IFS Cloud on my consulting site. Moving stock between your own sites is a different object, described in IFS Cloud Shipment Order: Move Stock Between Sites.

1.What is the difference between a shipment and a consolidated shipment?

A shipment is the IFS Cloud object that carries goods from one party to one receiver address, and a consolidated shipment is one departure of several shipments from a site. The 25R2 page About Shipment states both rules: one shipment can only go to one receiver address, and the consolidated shipment covers all the delivery addresses of the shipments connected to it.

Question Shipment Consolidated shipment
What it groups Order lines and other source lines Whole shipments
Addresses One receiver address, saved on the shipment All delivery addresses of the connected shipments
Typical use Several orders for one customer address leave as one delivery Customers on one route or one truck leave together
Created Automatically by the shipment type or manually from a shipment header Manually, or automatically when the shipment type toggle is enabled
Work done on it The full flow: reserve, pick, pack, complete, deliver All shipment activities except report picking, for example create pick list, deliver and print the shipment delivery note

The design rule follows from the table: group by receiver address in the shipment, group by departure in the consolidated shipment. A request to put two customers into one shipment is a request for a consolidated shipment.

2.How the shipment type decides what gets consolidated

The shipment type is the basic data record that controls how the shipment process runs, so a shipment that groups the wrong lines is checked against its shipment type first. The 25R2 page Add or Modify Shipment Types lists what it holds.

Shipment creation point

The Shipment Creation setting on the shipment type decides two things for customer orders: the trigger (order release or pick list creation) and whether IFS Cloud creates a new shipment every time or adds the line to an existing one. The shipment types installed with IFS Cloud show the combinations: NA (Not Automatic), NR (Create New Shipment at Release), AR (Add to Existing Shipment at Release), NP (Create New Shipment at Pick List Creation) and AP (Add to Existing Shipment at Pick List Creation). With an NR or NP type every release or pick list opens its own shipment, so lines from separate releases or pick lists never join the same shipment. Creation at release gives the warehouse a shipment early and suits planned routes. Creation at pick list creation waits until stock is reserved and is the safer choice when order lines change after release.

Where the shipment type comes from

A default shipment type can be set per site, per customer delivery address or per supply chain relation. For customer orders the supply chain relation wins, then the customer delivery address, then the site, and the value fetched to the order can be changed by hand. When an order gets the wrong shipment behaviour, this default chain is where to look; it is documented on Enter Shipment Process Parameters.

Consolidation parameters

With an Add to Existing type (AR or AP), consolidation parameters on the shipment type decide whether a new order line joins an existing shipment or starts a new one. With planned ship date and route as parameters, only order lines with the same planned ship date and route are connected automatically to the same shipment. The parameters are not checked when a user connects a line manually, so a manual connection can mix ship dates that the automatic rule would keep apart.

Events and optional events

The shipment type sets which events in the flow run automatically and which wait for a user. Optional events hang on a main event, for example generating a handling unit structure or printing transport labels when the pick list is created. The implementation decision is where the flow stops: a site with manual packing stops before Complete, a site with fixed packing rules lets the flow run through.

3.The shipment flow, step by step

A shipment moves from Preliminary to Completed to Closed, and the work between those statuses is reservation, picking, packing and delivery. The order of steps below follows the 25R2 About Shipment page.

  1. Connect order lines. Customer order lines can be connected in the Released, Reserved, Picked or Partially Delivered status, either automatically by the shipment type or manually. A new shipment starts in Preliminary.
  2. Create one pick list. The Create Pick List command in the shipment header creates a consolidated pick list for the shipment. Customer order lines are not mixed with pick list lines from other sources, so a shipment holding both gets two pick lists. Picking itself is covered in Advanced Picking Strategies in IFS Cloud.
  3. Consolidate and pack. Picked goods can be placed in shipment inventory, where consolidation and packing happen. The handling unit structure is built here, manually or automatically.
  4. Complete. When the shipment is packed and ready for delivery it gets the Completed status. Changes after that require turning the shipment back to Preliminary with Undo Complete; with shipment inventory, the quantity to deliver can still be changed in Completed.
  5. Deliver and close. Delivery covers only shipment lines that are picked partially or completely. After delivery the dispatch advice can be sent and resent. A delivery can still be reversed with Undo Delivery, which returns the shipment to Completed, and Undo Complete then takes it back to Preliminary for changes. Once the shipment is Closed, its content is final.

Goods that reach shipment inventory and never get delivered are the gap this flow leaves open. The causes and the daily check are in Stock Picked but Never Shipped in IFS Cloud.

4.Handling units: the physical structure of the shipment

A handling unit is the IFS Cloud name for any container goods are packed in, and handling units can be nested, for example small boxes in big boxes on a pallet. IFS Cloud does not require a handling unit structure on a shipment. Without one, though, there is no accurate weight and volume per container, which is the data the carrier and the transport capacity check need. The details are on About Handling Units.

  • Net and tare weight are calculated for each handling unit from the weights of parts, handling unit types and accessories.
  • An SSCC can be created for every level of the structure, so a pallet and each box on it can carry their own label.
  • Handling unit types (pallet, carton and so on) need volume and weight in basic data, otherwise the Packing Proposal skips them.

The Packing Proposal attaches shipment line reservations to an optimal number of handling units of an optimal size. It can be set on the shipment type and is then the default for new shipments, with the option to change it on the shipment. Parts without volume or weight are left out of the calculation, which is the first thing I check when a proposal packs less than expected. The setup is explained in Mastering the Packing Proposal, and the 25R2 reference is About Packing Proposal.

5.Connecting shipments to a consolidated shipment

A shipment can be connected to a consolidated shipment only when both belong to the same site and neither has been delivered. The 25R2 page Connect to/Disconnect from Consolidated Shipment adds three more conditions: the shipment is not connected to another consolidated shipment, it is not Cancelled or Closed, and loading is not finished.

Check capacity before you connect

The connect step can compare the transport capacity with the weight and volume of the shipments already connected and those you intend to connect. You mark the candidates on the Available Shipments tab and see whether the truck would be over capacity before anything is connected. The comparison needs a transport capacity defined first: weight and volume capacity entered by hand, a transport unit type entered on the consolidated shipment, or a transport unit type defaulted from the ship-via code. It is only as good as the handling unit weights from section 4.

Common values follow the connected shipments

The consolidated shipment shows a parameter such as route or forwarder only while it is common to all connected shipments. Connecting a shipment with a different value clears the parameter, and disconnecting the odd one out restores it.

Loading order

Loading onto the transport vehicle is needed before delivery and can be handled in IFS Cloud. A load sequence can be entered or defaulted from the route, and the activities that prepare shipments for loading are sorted in load sequence. When a delivery note is printed from the consolidated shipment, the sorting follows the reversed load sequence.

6.What to set up before the first consolidated shipment

Consolidation works only when the shipment type, the defaults and the packing data agree, and each of these items is set in basic data rather than on the order.

Setting Where What goes wrong if it is missing
Shipment creation point Shipment type Shipments are not created, or are created before the order lines are stable
Default shipment type Site, customer delivery address, supply chain relation Orders pick up the site default and ignore the rules meant for one customer
Consolidation parameters Shipment type Lines with different ship dates or routes end up in one shipment, or every line gets its own
Automatic Creation of Consolidated Shipment Shipment type (disabled by default) Every consolidated shipment has to be created and filled by hand
Handling unit types with volume and weight Handling unit basic data No calculated weight per container, so the capacity check relies on gross weights updated by hand; Packing Proposal skips the type
Delivery note grouping Shipment type consolidation parameters for shipment lines The customer receives one note when it expects one per order, or the reverse

A wrong or missing delivery address breaks the first rule of the shipment, because the address is what separates one shipment from the next. Sales Order With No Delivery Address in IFS Cloud covers how that happens and how to catch it.

Once shipments are built this way, the next step is usually sending them to the carrier without retyping. The IFS Cloud to ROHLIG SUUS Logistics interface sends shipment details to the forwarder when a shipment is released and links the booking reference back to the shipment.

7.Frequently asked questions

Can I consolidate orders from different customers in IFS Cloud?

Orders from different customers can leave together in IFS Cloud, but not in one shipment, because a shipment goes to one receiver address only. Each customer address gets its own shipment, and the shipments are connected to one consolidated shipment, which represents a single departure from the site to all their delivery addresses.

Does an IFS Cloud shipment print one delivery note or one per order?

The number of delivery notes for an IFS Cloud shipment depends on the delivery note consolidation parameters in the shipment type. With no parameters, one delivery note is created for the full shipment. Parameters such as Source Ref 1 or Reference ID split the shipment lines into separate delivery notes by that value.

Can I add an order line to an IFS Cloud shipment that has already been picked?

An order line can be added to an IFS Cloud shipment while the shipment is in Preliminary status, and the line itself can be Released, Reserved, Picked or Partially Delivered. A Completed shipment goes back to Preliminary with Undo Complete. A delivered shipment is first reversed to Completed with Undo Delivery. Only a Closed shipment is final.

Why does IFS Cloud create a new shipment instead of adding the line to the open one?

IFS Cloud creates a new shipment every time when the shipment type is a Create New Shipment type, such as the installed NR (Create New Shipment at Release) or NP (Create New Shipment at Pick List Creation). With an Add to Existing type (AR or AP), a new shipment is created when the order line does not match the consolidation parameters of the shipment type, for example a different planned ship date or route. The order line can still be connected manually to the open shipment, because consolidation parameters are not checked on manual connection.

Do I need handling units to use consolidated shipments in IFS Cloud?

Handling units are not mandatory for an IFS Cloud shipment or consolidated shipment. They are needed for an accurate weight and volume per container, for SSCC labels, for the Packing Proposal and for a meaningful transport capacity check when shipments are connected to a consolidated shipment.

8.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.

Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.

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

Send your IFS Cloud shipments to the forwarder without retyping

The ROHLIG SUUS interface is built on IFS Workflow with no middleware. It books the transport from the shipment and logs carrier errors on the shipment header, so your team fixes and resends without leaving IFS Cloud.

See the ROHLIG SUUS interface Read: Mastering the Packing Proposal

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

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

Get Detailed Report

Enter your details to receive a detailed ROI report.