We’re planning warehouse management integration for our ICS 2023-1 environment and debating between standard ION integration versus custom API development.
ION Standard Integration:
Leverages pre-built BODs for inventory, shipments, and receipts. Provides out-of-box connectivity but may lack flexibility for our specialized warehouse workflows. Upgrade path is straightforward with Infor support.
Custom API Integration:
Direct REST API calls to CloudSuite and WMS endpoints. Complete control over data mapping and workflow logic. Handles our unique cross-docking and kitting requirements that standard BODs don’t support well.
Our WMS vendor supports both approaches. Main concerns are upgrade complexity, long-term support implications, and whether a hybrid model makes sense. Has anyone successfully implemented hybrid integration models combining ION for standard transactions with custom APIs for specialized workflows?
We use Dell Boomi to manage both ION and custom API integrations in one platform. This provides unified monitoring, error handling, and logging across both patterns. For support, Infor will help with ION-related issues but custom API problems are your responsibility unless they’re proven CloudSuite API bugs. Document your integration architecture thoroughly - clearly delineate which workflows use ION versus custom APIs. This helps during troubleshooting and upgrade planning. Also budget for additional testing effort during CloudSuite upgrades to validate custom API compatibility.
The hybrid approach sounds reasonable. How do you manage the complexity of maintaining two integration patterns? Do you use different middleware or handle both ION and custom API connections through the same integration platform? Also, what’s been your experience with Infor support when issues arise in hybrid implementations - do they support both layers or only the ION portion?
Hybrid is definitely viable and often the best approach. Use ION for core WMS transactions - inventory adjustments, shipment confirmations, receipt processing. These are well-supported with standard BODs and handle 80% of typical scenarios. Then layer custom APIs for your specialized workflows like cross-docking orchestration and complex kitting logic. This gives you upgrade stability for the bulk of integration while maintaining flexibility where needed. Just ensure your custom APIs use stable endpoints that Infor commits to supporting long-term.