Welcome to Intershop Order Management 3.7!
Intershop Order Management (IOM) is an application of the Intershop Commerce Suite (ICS) that is designed to combine omni-channel commerce processes into one system. It automates and streamlines the life cycle of orders and payments. IOM processes orders from multiple touch points (web shop, mobile shop, call center and more), allocates them to multiple fulfillment solutions (fulfillment centers, drop-ship distributors, physical stores and more), and tracks all order and payment transactions.
IOM offers a centralized platform for managing distributed inventory, order, invoice and payment life cycles, and provides call center functionality, enabling real-time visibility into customers' purchasing behavior, stock levels, payments, and more. As part of ICS, it utilizes the suite's transaction, PIM and merchandising features.
IOM offers the possibility to tailor your business models as flexible and free as you need and depict them in your e-commerce environment. The order management system adjusts the order processing for various sales channels and suppliers and can be seamlessly integrated with existing components of your IT environment.
|API||Application Programming Interface|
|Docker||An operating system-level virtualization software. Also see Kubernetes and Helm.|
A package manager for Kubernetes. Also see Docker.
|ICM||Abbreviation for Intershop Commerce Management|
|IOM||Abbreviation for Intershop Order Management|
An open-source system for automating deployment, scaling, and management of containerized applications. Also see Docker and Helm.
|OMS||Abbreviation for Order Management System, the technical name of the IOM|
|OMT||Abbreviation for Order Management Tool , the graphical management tool of the IOM|
|REST||Representational State Transfer|
This feature is only accessible, if IOM Helm Charts of version 1.6.0 or newer are used. The new IOM Helm Charts are now providing the parameter jboss.activemqClientPoolSizeMax, which enables the configuration of size of ActiveMQs client thread pool.
The following metrics have been added to the /metrics endpoint:
|application_iom_shared_fs_disk_usage_ratio||Disk usage ratio - float value range [0..1] - 0 = 0%, 1 = 100%|
|application_iom_shared_fs_disk_total_bytes||Total shared fs size in bytes|
|application_iom_shared_fs_disk_used_bytes||Used shared fs size in bytes|
The following infrastructure components were updated:
IOM is now running in Wildfly 25.0.1.Final. Projects have to use the update dependencies to this version of Wildfly.
For installation instructions see:
Docker-images are available at:
Helm Charts are available at:
|71467||Usage of Maven-Artifacts as input for caas2docker is deprecated|
|70704||Removed obsolete feature Order Merge #3|
|52880||Queues might cause OOM exception in high load scenarios|
|69833||Approval responses for custom order approvals are not post-processed|
|70659||StateHistory - inconsistent sorting behaviour|
|70901||Order processing fails when order for new customer address is created without first name|
|70904||Slow order search performances due to missing indexes on OrderPosDOs|
|71213||"Returns"-tab in OMT might break in case of invalid/unprocessed returns|
|71258||StateControllers should write objectIds to log additionally|
|71269||Return label documents are not showing in OMT when the document supplier is not the selected shipping supplier|
|71451||Wrong/missing index on database table ShippingBucketPropertyDO|
|71561||Dynamic taxes may lead to exceptions with the FinanceController|
|71735||Order total (gross and net) in OMT are wrong|
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.