I am reporting a significant logic gap in how IFS Cloud handles date calculations for pegged Shop Orders. Currently, when a Shop Order finishes early, the Planned Ship Date on the Customer Order line pulls forward based on production availability, but the Planned Delivery Date remains static.
The Logic Flaw: IFS currently treats the Planned Ship Date as the "earliest possible" date rather than the "required" date based on Planned Delivery. This creates a logical paradox in the system.
Example Scenario:
-
Customer Requirement: Planned Delivery is Day 25 with a 2-day transit (DLT). The Planned Ship Date should be Day 23.
-
Early Build: The Shop Order is rescheduled to finish on Day 1.
-
IFS Result (Due Date): Moves to Day 2. This is correct; it reflects that the item is physically in stock early.
-
IFS Result (Ship Date): Pulls all the way forward to Day 3 (Day 2 + Picking Lead Time).
-
The Disconnect: Planned Delivery stays at Day 25. This creates an illogical 22-day gap for a 2-day transit. The system essentially assumes the carrier will hold the freight for three weeks.
Business Impact:
-
Shipping Blindness: Because the system-generated dates are no longer trustworthy, the shipping team is forced to ignore Planned Ship Dates and manage the schedule manually.
-
Early Delivery Penalties: Many of our customers have strict "No Early Delivery" windows. The current logic forces manual back-calculation of ship dates to avoid heavy fines.
-
Metric Inaccuracy: This breaks OTD tracking. We can ship on time for the customer requirement but be flagged as "late" because we missed the pulled-forward, production-driven ship date.
The Constraints: There is currently no manual way to resolve this in-system even if that were feasible (which would be inefficient anyway). We cannot update the CO line without moving the required delivery date, and IFS does not allow a direct override of Planned Ship or Planned Due on any CO lines without shifting the entire manufacturing schedule.
Required Solution: If changing the logic completely isn't an option since the "earliest possible" view might have value in some cases, IFS needs a setting that allows the user to choose the anchor for the ship date (as it currently does OR as I'm suggesting). We need the option to keep the shipment tethered to the delivery requirement. This ensures the gap correctly exists between Planned Due (In Stock) and Planned Ship—reflecting the reality of the item sitting in the warehouse until it is actually required to move.
Is this behavior being addressed in a future update, or has anyone developed a robust workaround to keep these dates synced?