Many customers are using Supplier Agreements with Blanket Orders in IFS to support long‑term, pre‑approved contracts and enable efficient call‑off purchasing via agreement releases. This approach works well for recurring goods and services by reducing approvals, enforcing agreed prices, and streamlining operational procurement.
In practice, however, several areas are commonly raised for discussion when using this functionality:
-
Authorization and control model
Blanket Orders are treated as pre‑authorized by design. Releases generated from these agreements do not trigger PO authorization, even when values change due to additional lines or charges. This often leads to questions around governance, delegation of authority, and audit compliance. -
Handling of value changes and charges
Additional costs or changes to the PO value are considered part of the already approved blanket commitment. While this aligns with the original concept, it can be challenging for organizations that expect authorization to be triggered on value increases or deltas. -
Flexibility versus risk
The functionality favors flexibility and user responsibility over restrictive system controls. Some customers see this as a strong benefit, while others experience it as a risk—especially in regulated environments or project‑driven cost control models. -
Alignment with business processes
Differences in procurement operating models, financial controls, and project governance mean that the standard Blanket Order behavior does not always align with internal policies or expectations. -
“Working as designed” vs. business expectations
Many behaviors are intentional and long‑standing in IFS, yet still create challenges in real‑life usage. This raises recurring questions about whether gaps should be addressed through process changes, configuration options, or future product enhancements.
Given these points, it would be valuable to hear from other IFS customers and users:
- How are you using Supplier Agreement – Blanket Orders today?
- What challenges or limitations have you encountered?
- How do you manage authorization, value changes, or additional charges?
- Do you see the current behavior as a benefit, a risk, or both?
- Are there enhancements or configuration options you believe are missing?
Sharing experiences and lessons learned can help establish best practices and guide future improvements.
