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.
|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|
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.
The following infrastructure components were updated:
IOM is now running in Wildfly 23.0.1.Final. Projects have to use the updated dependencies.
The IOM REST API Order 2.2 offers additional endpoints to:
The specification can be found in the delivery doc/REST/ or in the Knowledge Base.
For installation instructions see:
Docker-images are available at:
Helm Charts are available at:
|61757||[IOM-10955] Deprecated set|isManuallyCorrected() and set|isDifferenceAt*() of ResponsePosDO, use get|setIsManuallyCorrected() and get|setIsDifferenceAt*() instead|
|61884||[IOM-10969] Deprecated get|setResponsePosPropertyList of ResponsePosDO, use get|setPropertyList() instead|
|62380||[IOM-11110] Deprecate mergeTypeDefRef in OrderStateAO|
|62397||[IOM-11113] Deprecated obsolete PersistenceUtils.getMergedOrderJoin(String orderAlias, String orderPosAlias)|
|62988||[IOM-11175] Deprecated obsolete classes and methods that are used by the already deprecated order state service|
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
|62378||[IOM-11109] Removed references to obsolete feature Order Merge in class OrderDO|
|63280||[IOM-11233] Removed setTaxDO() of InvoicingSalesPricePosDO, InvoicingSalesPriceChargeDO, PaymentSalesPricePosDO and PaymentSalesPriceChargeDO|
Possible database migration error due to a trigger definition
|61983||[IOM-10989] Exception in OMT for disabled Shop2SupplierDOs|
|61986||[IOM-10990] NPE in reservation for disabled Shop2SupplierDOs|
|62131||[IOM-11030] OrderStateMapperUtil provides incorrect subtotal net price|
|62147||[IOM-11031] Doubled JoinColumns hide persistence errors (e.g. OneToOne Relation in DispatchPosItemDO to OrderPosDO should be ManyToOne)|
|62206||[IOM-11061] Credit note processing fails in some return scenarios (manual credit notes)|
|62377||[IOM-11108] Tax rate returns message key instead of error message|
|62513||[IOM-11125] AddressLocationPackstation for invoice addresses returns message key instead of error message|
|62678||[IOM-11137] Blocked schedules due to undefined FTP connection timeout|
|62755||[IOM-11150] Stock import fails if there are only 2 lines and both lines are related to the same SKU|
|62766||[IOM-11152] YAML-specification of REST-API order order-states misses returned objects and attributes|
|62895||[IOM-11164] Missing data type in Cancellation(Pos)-v1.0.xsd|
|62965||[IOM-11169] Unable to edit product stock data in OMT|
|63070||[IOM-11206] Migration scripts don't create InvoicingSalesPricePosTaxDO records|
|63261||[IOM-11226] REST order creation fails with 500 if rate of multiple taxes is 0|
|63264||[IOM-11227] Deprecations related to the multitaxes are not correctly implemented|
|63278||[IOM-11232] Selected attributes are not stored if not required|
|63395||[IOM-11261] Blocked reserved stock not counted in OMT (shop hierarchy)|
|63399||[IOM-11263] Undocumented (breaking) change in address mapping behavior|
|63548||[IOM-11278] Order import fails when passing multiple tax records with rate zero|
|63655||[IOM-11292] Undocumented value-constraint at position.number which doesn't allow negative numbers|
|63659||[IOM-11293] Invalid rounding of order level promotions on the orderPosItemsDOs|
|63741||[IOM-11310] Undocumented constraints at prices in REST-APIorder, net must not be greater than gross, amountDiscounted must not be greater than amount|
|63835||[IOM-11317] Order charge taxes are distributed incorrectly|
|63879||[IOM-11320] REST Order API uses same attribute 'selectedSupplier' for different information|
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.