Introduction

Welcome to Intershop Order Management 3.5!

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.

Glossary

General Information

• Feature List - Intershop Order Management 3.5
• System Requirements - Intershop Order Management 3.5
• Guide - Intershop Order Management - Technical Overview
• Guide - Operate Intershop Order Management 3.X
• Overview - IOM 3.4- 3.5 Migration
  and
• Public Release Note - IOM Helm Charts 1.5
• Public Release Note - IOM dbaccount Docker Image 1.2.1.0

Additional References

• See Overview - IOM Public Release Notes for an appropriate version of the ICM-IOM-Connector
• Overview - Intershop Order Management REST API
• Overview - IOM Interfaces
  and
• Reference - IOM REST API - Order 2.2
• Overview - IOM Order Change

New Features and Enhancements

Change of Orders

With the IOM Order REST API 2.2, IOM now supports creating change requests for an order in certain statuses using a REST API, see Reference - IOM REST API - Order 2.2.

See Concept - IOM Order Change to get more insights for this first MVP. The Cookbook - IOM Order Change explains selected use cases.

Enhancements in Setup and Operations

Update of Infrastructure Components

The following infrastructure components were updated:

• IOM application image is now based on ubuntu:20.10
• IOM now uses AdoptOpenJDK 11.0.11+9

Customization

IOM is now based on Wildfly 23.0.1.Final

IOM is now running in Wildfly 23.0.1.Final. Projects have to use the updated dependencies.

Interfaces

New Version of IOM REST API Order 2.2

The IOM REST API Order 2.2 offers additional endpoints to:

• Get an order
• Create an order change request
• Get an order change request
• Get all order change requests of an order

The specification can be found in the delivery doc/REST/ or in the Knowledge Base.

For more information also see Reference - IOM REST API - Order 2.2 and Fixed Defects below.

Setup & Configuration

For installation instructions see:

• Guide - Intershop Order Management - Technical Overview
• Guide - Operate Intershop Order Management 3.X

Docker-images are available at:

• docker.intershop.de/intershop/iom-config:3.5.0.0
• docker.intershop.de/intershop/iom-app:3.5.0.0
• docker.intershop.de/intershop/iom-dbaccount:1.2.1.0

Helm Charts are available at:

• repository.intershop.de/helm

Interfaces

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

Deprecations

Also deprecated are:

• get|setReturnPosTransmissionPropertyList() of ReturnPosTransmissionDO, use get|setPropertyList() instead

• get|setReturnPosPropertyList() of ReturnPosDO, use get|setPropertyList() instead

• get|setReturnItemPropertyList() of ReturnItemDO, use get|setPropertyList() instead

• get|setReturnTransmissionPropertyList() of ReturnTransmissionDO, use get|setPropertyList() instead

• get|setResponsePosTransmissionPropertyList() of ResponsePosTransmissionDO, use get|setPropertyList() instead

• Shop2SupplierDO.getSupplierSupportsCOD(), use isSupplierSupportsCOD() instead

• CommunicationDO.isActiveOMT(), use getActiveOMT() instead

• get|setIsDoProcess(), set|getIsDoManualApprove() of PaymentActionApprovalDefDO, set|isDoProcess(), set|isDoManualApprove() instead

• SupplierOrder.getOrderPosDOList(), use getOrderPosDOList instead

• OrderDO.getBillingAddresses(), use getBillingAddress() instead

Please also see Guide - IOM 3.5 Deprecations and Removals for more details about IOM-11175 - Deprecated obsolete classes and methods that are used by the already deprecated order state service

Removals

Fixed Defects

Possible database migration error due to a trigger definition

Changelog