Welcome to Intershop Order Management 3.3!
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|
|SOAP||Simple Object Access Protocol|
In older versions of IOM, heap dumps were written to stdout in order to get catched by the monitoring system. They are now stored in the sub-directory dumps of IOM's shared file-system. The naming conventions of dump files are: java-<pod name>-<time stamp (start time)>.hprof.
Using these naming conventions, heap dumps are never overwritten, they can be assigned to pods (and therefore aligned to error messages) and they can be sorted over time.
IOM is now running in Wildfly 21.0.2.Final. Projects have to use the updated dependencies.
Queries with the JPA Criteria API are supported now. Therefore the a dependency to org.hibernbate:hibernate-jpamodelgen was added to
For installation instructions see:
Docker images are available at:
There are no deprecations for this release.
There are no removals for this release.
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.