Related Documents
Document Properties
Last Modified
Added to KB
Public Access
Doc Type
Release Notes
IOM 3.2

Public Release Note - Intershop Order Management 3.2

1 Introduction

Welcome to Intershop Order Management 3.2!

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.

1.1 Glossary

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

APIApplication Programming Interface
DockerAn operating system-level virtualization software. Also see Kubernetes and Helm.

A package manager for Kubernetes. Also see Docker.

ICMAbbreviation for Intershop Commerce Management
IOMAbbreviation for Intershop Order Management

An open-source system for automating deployment, scaling, and management of containerized applications. Also see Docker and Helm.

OMSAbbreviation for Order Management System, the technical name of the IOM
OMTAbbreviation for Order Management Tool , the graphical management tool of the IOM
RESTRepresentational State Transfer
SOAPSimple Object Access Protocol

2 General Information

3 Additional References

4 New Features and Enhancements

4.1 Enhancements in Setup and Operations

4.1.1 On/Off for Access Log

In combination with IOM Helm Charts 1.2.0 it is now possible to control the creation of access log messages.

See Public Release Note - IOM Helm Charts 1.2.0 and Guide - Operate Intershop Order Management 3.X.

4.1.2 Update of Java to Version

IOM 3.2 uses Adopt OpenJDK now.

Also, see System Requirements - Intershop Order Management 3.2.

4.2 Customization

4.2.1 Allow Usage of a Docker-Proxy, When Building Project Images

A new property DOCKER_PROXY was added to the tool caas2docker. This property can be used to avoid direct access to Docker Hub. 

The DOCKER_PROXY property can be filled with the name of an alternative Docker repository, which acts as a proxy for Docker Hub.

See also the example property files provided with caas2docker.

4.2.2 Timeout for Test-data Import is Configurable at Runtime Now

In combination with IOM Helm Charts 1.2.0 it is now possible to set a timeout for importing test data at runtime by using the new Helm parameter caas.importTestDataTimeout.


Setup & Configuration

For installation instructions see:

Docker-images are available at:


5 Interfaces

For a complete list of all interfaces please see Overview - Intershop Order Management REST API and Overview - IOM Interfaces.

5.1 Deprecations

5.2 Removals

Key Summary

6 Fixed Defects

Key Summary
IOM-10817 Incorrect order state determination after export failures #3
IOM-10773 The order state REST API does not return the price total
IOM-10743 Order calculation with free items has a wrong redistribution of order level promotions
IOM-10741 Order calcuation may fail due to a wrong usage of BigDecimal.divide method
IOM-10732 Duplicated error text at return message positions
IOM-10726 When editing customer addresses the street number is wrongly defined as required
IOM-10700 Unable to store a POBox address as customer shipping address
IOM-10690 Saving an erroneous edited return/cancellation fails in OMT
IOM-10689 Positions are not sorted in the shipping buckets
IOM-10684 A credit validation for a return may fail after a manual credit note
IOM-10682 Customer mail creation doesn't work anymore, because of empty street()
IOM-10678 ShippingBuckets not sorted in manual credit note creation dialog
IOM-10677 Cancellation of a previous manual credit note has a missing reference
IOM-10666 NPE in OMT when trying to save modified cancellation
IOM-10657 Missing credit amount with a mix of cancellation and return
IOM-10654 Wrong available charge amounts within the manual credit form
IOM-10651 Unable to create a manual credit note on a shipping bucket charge only
IOM-10647 SFTP broken
IOM-10640 The error texts of pending refunds are not reset when the refund gets processed
IOM-10638 Scripts of dbaccount-images are writing passwords into log messages
IOM-10623 Payment due date wrong date format when selected from calendar
IOM-10622 Wrong logic in OrderPosItemMappingPTBean with retry processes
IOM-10619 Formatting of modification date at customer details page is wrong
IOM-10615 Erroneous supplier messages (missing permission because of failed supplier assignment) should be more detailed
IOM-10612 Unable to return all items using multiple returns
IOM-10608 Order state report lists status of invalid dispatches as dispatched
IOM-10594 Wrong invoice calculation with order-level promotions
IOM-10591 The help-link to the online help is one of an older version
IOM-10546 Encoding of Åland Islands is not correct in OMT
IOM-10543 Wrong amounts in PaymentInformationDO with partial payments
IOM-10362 Secure flag is missing on security related cookies
IOM-10361 Set httponly-flag on security related cookies
IOM-10205 CustomerAddressDO is identified as duplicate despite different house number
IOM-9847 Editing product data always changes the currency to EUR
IOM-9754 Wrong order position item mapping for invoicing


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.

Customer Support
Knowledge Base
Product Resources