Welcome to Intershop Order Management 3.6!
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 touchpoints (webshop, 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 Intershop Commerce Platform, it utilizes the its 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|
The following improvements are now available:
DocumentPropertyDOwas enhanced to inherit the common property.
Improvements in setup and operations are:
Also, see Public Release Note - IOM Helm Charts 1.5 and Public Release Note - IOM dbaccount Docker Image 1.3 for all changes in detail.
For installation instructions see:
Docker-images are available at:
Helm Charts are available at:
|69685||Deprecated get*PosList() of ResponseDO, ReturnDO, DispatchDO and OrderCancelDO, use get*PosDOList() instead|
|69744||Deprecated CustomerAddressLO and get|setCustomerAddressLO() of ShopUserMailLO|
|69747||Deprecated get|setPropertyList() and getPropertyValue(String) of DocumentDO, use get|setPropertyList() and getPropertyValue(String, String) instead)|
|69753||Deprecated getQuantity() of ReturnPosDO, use getQuantityReturned() instead|
|70203||Depreacted bakery.util.enumsSortingOrder, use com.intershop.oms.utils.enums.enumsSortingOrder instead|
|57774||Removed obsolete feature Order Merge #2|
|62398||Removed deprecated PersistenceUtils.getMergedOrderJoin(String, String)|
|69687||Removed deprecated mergeTypeDefRef() of OrderStateAO|
|69697||Removed obsolete getOrder2OrderPosMap(), getResponse2ResponsePosMap(), getDispatch2DispatchPosMap(), getReturn2ReturnPosMap() of MapGenerator|
|69698||Removed obsolete checkOrderAddressesAreEqual(), checkOrderAddressCompaniesAreEqual() of OrderLogicservice|
|69699||Removed obsolete getOrderPosNo() of bakery.logic.communication.mapper.MapperUtil|
|69741||Removed deprecated createErrorResponse() and createErrorResponseWithList() of ApiResponseService|
|69742||Removed deprecated loadOrderHeader(String, String, long) of OrderSecurityService|
|70216||Removed obsolete process tasks SplitReturnPTBean, CreateSuperResponsePTBean, SplitReturnPTBean, CreateSuperReturnPTBean, SplitDispatchPTBean and CreateSuperDispatchPTBean|
|70217||Removed obsolete jpdl-files and corresponding queues ProcessResponse4OrderMerge(.xml), ProcessDispatch4OrderMerge(.xml), ProcessReturn4OrderMerge(.xml)|
|60170||Removed deprecated import.properties as part of test-data in projects, use new Helm parameter caas.importTestDataTimeout instead|
Included in "Removed obsolete feature Order Merge #2", the following removals were done:
|63337||File transfer jobs are stuck after failovers or restarts|
|63574||OMT displays shipping buckets not sorted by number ascending|
|64040||Order change requests do not work with modifications in some json elements|
|64049||Unappliable order change request never leaves status ACCEPTED|
|64618||Order Calculation: possible wrong distribution of order level promotions on the order positions|
|64623||REST API/order returns RuntimeExceptions when using just net or just gross values at order creation|
|65071||OrderTransmission canceled automaticaly|
|65527||Performance issues due to missing indexes|
|65559||Very slow display of the order positions details in OMT|
|65652||Order change request: Promotions cannot be removed|
|65676||Order change request: Charges of a shipping bucket can't be removed|
|65683||Order change request: Positions can't be removed|
|65687||Moving positions between buckets don't work|
|69384||Using order change requests, moving an object with an ID/number to another parent is not possible (moving as in delete+create in one request for example)|
|69721||User/permission management is still ways to slow by supplier onboarding|
|69854||Orders with 1000 positions cannot be dispatched using OMT|
|69876||Import performance issues when using Azure DB for PostgreSQL|
|69930||Performance issues with large orders|
|70004||Job Framework gets stuck in case of long-running jobs|
|70116||Fixing wrong product data by import is impossible|
|70126||Schedules are stuck after exceeding the configured "expectedRuntime"|
|70559||PaymentNotificationLogicBean is missing discounted amount for positions|
|70628||Regression in ValidateResponsePTBean due to removal of ShopDO.shopUsesOMT|
|72857||RMA uses wrong shop-name in OMT|
|71735||Order total (gross and net) in OMT are wrong|
|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|
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.