Welcome to Intershop Order Management 2.9!
Intershop Order Management is an Intershop Commerce Suite orders and payments. Intershop Order Management 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. that is designed to combine omni-channel commerce processes into one system. It automates and streamlines the life cycle of
Intershop Order Management 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 Suite, it utilizes the suite's transaction, PIM and merchandising features.
Intershop Order Management (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.
|Intershop Order Management||Intershop Commerce Management B2X||IOM Connector|
|API||Application Programming Interface|
|FTP||File Transfer Protocol|
|GDPR||General Data Protection Regulation|
|ICM||Abbreviation for Intershop Commerce Management|
|IOM||Abbreviation for Intershop Order Management|
|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|
|RMA||Return Merchandize Authorization|
|SOAP||Simple Object Access Protocol|
A new REST API enables companies to respond quickly when customers ask to view all their personal data, see Overview - Intershop Order Management REST API for more information.
If required, this data can also be deleted directly on the customer detail page.
The order routing process can now be simulated at the time of reservation, which means the relevant inventory is immediately reserved for the customer, see Concept - Reservation with Dynamic Order Supplier Evaluation for more information.Additionally the supplier selection process was improved to respect the rank of the supplier evaluation now.
The support of return requests (RMA - return merchandize authorization) was extended. Therefore:
The representative handling of a return can now create a return label for a specific customer or order, with the label being automatically e-mailed to the customer. It is also possible to send labels manually.
Pricing is now displayed according to the respective business model. Net for B2B and gross for B2C.
Additionally, prices for units are displayed with 5 decimal digits now, which can be necessary when prices are more detailed for a unit than just 2 decimals.
When having errors in processing they will be displayed now at the related tab and position on the order details page.
The following changes were made to improve the user interface:
Improvements for using customer e-mails are:
The new cluster property
is.oms.mail.resources.base.url can be used in templates as
$mailResourcesBaseUrl, i.e., for mail images or stylesheets that must have public access for mail clients.
ShopUserMailResponseLOis supporting confirmed and canceled quantities in e-mails
All partners in
PartnerReferrerDO can now be configured as receiver of a transmission, e.g., finance controllers and payment providers.
The new version comes with a set of new and improved REST-interfaces:
Additionally the documentation of the REST API was moved to a public domain of Intershop. Specifications can be downloaded here and used for automated REST-client generation for example.
Please see Overview - Intershop Order Management REST API for more information about the IOM REST API.
A public database documentation is now available, which shows all relevant tables, relations and enumerations for configuring business processes and features of the IOM, see Reference - IOM Database Documentation where to find it.
The export interface for OrderPlacement of suppliers supports now schema OrderService-v1.1.xsd, to export data received by the order service interface v1.2.
For product import and product export the article numbers of shops, suppliers and manufacturer has been increased to a max length of 500 characters, see Guide - IOM Product Import and Guide - IOM Product Export.
E-mails for business operations can be send from internal e-mails separated now. I.e., the link contact the administrator on the OMT-login is attached to the new cluster property
is.oms.mail.businessoperations.to, see Guide - Setup Intershop Order Management 2.9.
The new cluster properties
is.oms.smtp.pass can be used for mail server authentication now, see Guide - Setup Intershop Order Management 2.9.
Responses of health check requests can be cached now. Therefore set the new cluster property
is.oms.healthcheck.cachelivetime, see Guide - Setup Intershop Order Management 2.9 and Concept - IOM Server Health Check.
To automate the database migration a new script was introduced (for this and older versions), see Guide - IOM Database Migration (2.0 - 2.17) for more information.
The distribution package that contains the binary distribution of Intershop Order Management 2.9 is available in the Product Calendar and consists only of this file:
For installation instructions please see:
Please note that the installation requires installed and preconfigured:
For a complete list of all interfaces please see Overview - IOM Interfaces
|IOM-9340||Deprecated 'returnCharge', 'hasInformShopReturn', 'shopUsesOMT' of ShopDO|
|IOM-8719||Deprecated interfaces of MessageProducerPT and CheckSendDebitorPT|
|IOM-8338||Deprecated 'sendOffTimeInHours', 'supplierShopKey', 'immaterialArticleUrlValidityDuration' of Shop2SupplierDO|
|IOM-8257||Deprecated getQuantity of ShopUserMailResponsePosLO, use quantityConfirmed and quantityCanceled instead|
|IOM-8238||Deprecated "no" object attributes / path parameters in the GDPR REST API|
|IOM-7825||Deprecated 'Supplier Id as used by the shop' in SOAP-services|
|IOM-7439||Deprecated mail template registration processes|
|IOM-7436||Deprecated DocumentLayoutDO - persisted customer mail templates|
|IOM-7401||Deprecated AddressUtils.createAddressLO(ShopAddressDO shopAddressDO)|
|IOM-7399||Deprecated public methods of ShopUserMailLO|
|IOM-7398||Deprecated ShopAddressDO and ShopDO.shopAddressRef|
|IOM-8296||Removed obsolete 'allowedLoginTrials' from PlatformConfigDO|
|IOM-8196||Removed deprecated 'ListPrice', 'PurchasePrice', 'SalesPrice', 'salesPriceOld', 'provisionType', 'provisionPercentage', 'isBestseller' of product import|
|IOM-8195||Removed deprecated 'ListPrice', 'PurchasePrice', 'SalesPrice', 'salesPriceOld', 'provisionType', 'provisionPercentage' of product import|
|IOM-8172||Removed obsolete permissions about the tv-solution-kit|
|IOM-7562||Removed obsolete entries of ExecutionBeanDefDO and ExpandedExecutionBeanDefDO|
|IOM-7476||Removed obsolete registry of templates from jars and deployment directories|
|IOM-7215||Removed obsolete ReservedStockDO, DeficiencyStockDO, StockInformationDO and BookedStockDO|
|IOM-7011||Removed deprecated EVENT from ProcessTypeDefDO|
|IOM-8297||Missing localization key for return reason RET200|
|IOM-8289||HTTPS is not working for OMT|
|IOM-8285||Erroneous Response Validation for order partially canceled before export|
|IOM-8279||(Unexpected) Exception when throwing Exception in FTPFileTransferBean|
|IOM-8269||Several missing tool tips for indexed fields|
|IOM-8260||Typo in tooltip|
|IOM-8208||Mandatory order validation jobs are not mandatory after all|
|IOM-8138||When configuring directories for import, file-transfer and private keys, only absolute paths can be used|
|IOM-8116||Missing tool tip at most recent orders|
|IOM-8073||Missing tool tips at search form fields and result tables|
|IOM-8061||Missing permission handling on quick search box|
|IOM-8045||Hardcoded conditions for CASH_ON_DELIVERY modify partial cancellations|
|IOM-7990||Overlapping texts in OMT|
|IOM-7936||Missing "*" in "confirm payment" modal Dialog to mark the payment Method as required|
|IOM-7863||Background image too small for high-resolution monitors|
|IOM-7861||Comment while creating a manual credit note is not saved|
|IOM-7829||Concurrent creation of barcodes fails|
|IOM-7821||Atp- Reservation-Request is not filtering by Shop2Supplier restrictions|
|IOM-7685||Unable to sort the orders by their customer internal IOM ids|
|IOM-7669||Deleting a user in OMT must be done twice before it succeeds|
|IOM-7667||The blocked stock may not get modified according to an order modification.|
|IOM-7665||Velocity transformer throws exceptions in case of NULL values|
|IOM-7643||API-break because of non-deprecated deletion of getCountry() of userMailLO.getCustomerAddressLO()|
|IOM-7640||Exception is thrown if manual credit note is created for shipping costs only|
|IOM-7628||communication mapper v1_0: Wrong handling of the “#@#” separator between street name and house number.|
|IOM-7622||Customer name displayed at Order and Invoice pages is used from a shipping address|
|IOM-7612||Order quick search treats leading zeros as numeric id|
|IOM-7569||Reservation REST service does not save JSON response body in OrderMessageLogDO|
|IOM-7513||Usage of the wrong dispatch status after an erroneous dispatch|
|IOM-7497||Usage of the wrong return status after an erroneous return|
|IOM-7492||Missing tool tips at most customer mail actions|
|IOM-7448||NPE for delivery confirmation/ order cancelation when no supplier is selected (multiple suppliers selectable)|
|IOM-7425||Error(s) while retrieving information on Returns|
|IOM-7411||The button to create a new note is displayed even if the user does not have the according rights|
|IOM-7391||Invoice download only possible with permissions for OMS Internal Supplier|
|IOM-7386||The article lookup in parent shops is not recursive in the stock blocking process|
|IOM-7360||Rounding issue while creating correction positions in CreateInvoicing2ReturnPTBean|
|IOM-7359||Several issues with canceled ReturnDOs in CreateInvoicing2ReturnPTBean|
|IOM-7351||No tool tip on "mark as paid" at customer invoice details page|
|IOM-7347||Saving an organization assignment tree is too strict when not selected organizations are meanwhile deleted|
|IOM-7346||Customer link at search order table if permission "showCustomerData" not set for all shops|
|IOM-7344||Error page in OMT + Exception in calculation for invalid return messages|
|IOM-7321||Schedules remain locked, if backend server is stopped|
|IOM-7308||The database table Shop2FinanceControllerDO miss a unique index on (shopRef,financeControllerRef))|
|IOM-7304||Order Positions are not sorted in CreateCreditNote modal dialog|
|IOM-7286||Search for Orders in Customer Search delivers error|
|IOM-7285||Invoice/Credit note as attachment for dispatch/return mails isn't working|
|IOM-7276||Some invalid returns cannot be displayed in OMT and lead to a technical exception|
|IOM-7274||Error page in OMT + Exception in calculation for invalid return messages|
|IOM-7250||Customer search by phone with wildcard doesn't work|
|IOM-7245||Login page uses dropped system property is.oms.mail.administrator.to|
|IOM-7235||Invoice calculation broken for order level discounts|
|IOM-7226||Cannot change ArticleSupplierShopDetails in OMT for items with more than one ShopArticleNo|
|IOM-7223||Missing audit trail when canceling orders in approval state|
|IOM-7214||NullpointerException when creating return labels from ICM|
|IOM-7211||Document Service is not working|
|IOM-7202||Separator of daterangepicker has no spaces between two dates|
|IOM-7196||Several tables don't work in scroll mode on small screen width|
|IOM-7179||Manual credit notes are not considered correctly when creating credit notes for returns|
|IOM-7165||ShopCustomerMailLogicBean.createShopUserMailInvoicingLO inconsistent behaviour (Payment method)|
|IOM-7158||Wrong attribute handling in JAVA class ExpandedExecutionBeanDefDO|
|IOM-7154||Debtor/Invoice transmissions don't reset MessageLogContext and cause MessageLogException|
|IOM-7151||Retry mechanism for all transmission types broken in latest patch|
|IOM-7140||Search for order in "Waiting for approval" doesn't work|
|IOM-7136||Customer link at Order Details if no customer view permission|
|IOM-7134||ShopDO.getShop2FinanceController() isn't recursive|
|IOM-7128||Customer search breaks for a 3 level shop hierarchy|
|IOM-7125||Shop-Supplier check is wrong when looking for article availability in parent shop(s)|
|IOM-7122||OrderAuthorizationExpireControllerBean creates captures / invoices for orders with incomplete Payment|
|IOM-7121||ArticleExportConfigBeanDefDO.valueOf(Integer id) has wrong implementation|
|IOM-7120||Race condition causes Exception in ClosePaymentNotificationQueue when creating two notifications for the same order at the same time|
|IOM-7099||OrderRecallController / OrderRecallPC functionality is not working|
|IOM-7093||Cron schedules defined in the table ScheduleDO are not respected at the first run|
|IOM-7092||The lastRun attribute of ScheduleDO is set to the job creation date instead to the current time on the first run|
|IOM-7070||Disabling invoice creation via the active-flag is ignored|
|IOM-7061||discountedItem* prices for undiscounted items not mapped in OrderService 1.2|
|IOM-7058||The Postgres table ResponseTransmissionStates2StateGroupDefDO is not initialized|
|IOM-7044||Export files are deleted from the filesystem when the JVM/application server is shut down|
|IOM-7039||Comment form field overlaps label in return confirmation dialog|
|IOM-7034||cluster property is_oms_smtp_port is not in use|
|IOM-7007||All positions of an order are displayed as check failed allthough only some are|
|IOM-6902||Large set of warnings "Line 1 of a paragraph overflows the available area by more than 50 points"|
|IOM-6893||Large set of document warnings "fo:table-cell" is missing child elements. Required content model: marker* (%block;)+...|
|IOM-6844||Order search filter breaks when a shop hierarchy contains more than 2 levels|
|IOM-6840||FTP health check does not ensure file transfer|
|IOM-6726||Possible usage of wrong permission in tabs 'order cancellation' vs. 'product return'|
|IOM-6723||Customer Modify Permission is not considered in omt|
|IOM-6582||Soap CustomerService.storeCustomer fails because of optional addresses|
|IOM-6572||The default invoice address should be shown/ used in customer search instead of last modified address|
|IOM-6453||Misleading Error description in Order Response Validation|
|IOM-6435||Incomplete error message at return dialog|
|IOM-6211||race condition in OrderPersistenceBean may cause ConstraintViolationException|
|IOM-6203||Disabling of "Create credit note" button doesn't consider charges|
|IOM-6185||Permanent horizontal scoll bar in tables even if not neccessary|
|IOM-6070||Warning in invoice_credit_note_pdf.xslt|
|IOM-5488||ShopService storeResponse: parameter is used wrongly resp. documentation is wrong|
|IOM-5336||Generic attributes of order not readable in some cases|
|IOM-5334||Unchanged fields are reported as changed when using the CustomerService|
|IOM-5317||Reservation REST API: GET request should return 404 when object not found|
|IOM-5167||Broken tab icon in order system mail information|
|IOM-4939||Wrong Number of Suppliers at Search form for Shop/Supplier|
|IOM-4622||Uncomfortable/ non-possible usage of select box in several modal dialogs|
|IOM-4442||Add user history - select boxes lose their selected value after failed validation|
|IOM-4422||Permission handling for shown actions not implemented for change customer data|
|IOM-3477||Amount of invoices/ order positions is not displayed in the header of the related tab|
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.