Welcome to Intershop Order Management 3.0!
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.
Term | Description |
---|---|
API | Application Programming Interface |
Docker | An operating system-level virtualization software. Also see Kubernetes and Helm. |
Helm | A package manager for Kubernetes. Also see Docker. |
ICM | Abbreviation for Intershop Commerce Management |
IOM | Abbreviation for Intershop Order Management |
Kubernetes | 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 |
SOAP | Simple Object Access Protocol |
"A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries, and settings." (https://www.docker.com/resources/what-container)
The new version of IOM is delivered in form of Docker-images, which can be used directly or can be the base for further customizations in the context of projects.
Additionally, IOM Helm-charts are provided, allowing the automated operation of IOM in Kubernetes, especially in Intershop CaaS Environment..
For more information see:
With IOM 3.0 the OMT now displays the different shipping addresses in the section Shipping buckets including the position numbers that are assigned to the buckets.
Additionally, each position displays the assigned shipping address and shipping bucket (number).
The OMT is now showing ISO-4217 currency codes. See https://en.wikipedia.org/wiki/ISO_4217.
The standard currency codes are more cleary and have no redundancy than currency symbols.
IOM is now supporting PostgreSQL 12.
Also see System Requirements - Intershop Order Management 3.0.
Several properties are moved to be Helm-parameters and could be set at runtime now.
See Guide - IOM 3.0 Migration of Setup and Guide - Operate Intershop Order Management 3.X for more details.
It is now possible to delete standard IOM jobs, overwrite standard IOM jobs and to add custom jobs by defining them in quartz-jobs-custom.xml. Please note that the usage of quartz-jobs-cluster.xml is deprecated now.
See section quartz-jobs-custom.xml at Guide - IOM Standard Project Structure | Custom Properties for more details.
The enumeration DocumentTypeDefDO
can be extended now using ExpandedDocumentTypeDefDO.
Also see Guide - IOM 3.0 Migration of Customization and Delete - Overview - IOM Customization of Enumerations #3, especially Cookbook - Custom Enumerations.
The value SURCHARGE was added to ChargeTypeDefDO
and can now be used to better specify extra fees that are added to the regular costs, e.g. for shipping to remote areas.
Using the new REST API job-schedules and related information can be searched for and managed by runtime configuration.
The specification can be found in the delivery doc/REST/ or at Overview - Intershop Order Management REST API.
The usage of the currency was mostly decoupled from the shop's configuration at CountryDefDO
.
Therefore the currency code will be added to each order instance (OrderDO.currencyCode
) when placing the order and will be (and should be) used primarily from this location now.
Also see Guide - IOM 3.0 Deprecations and Removals for currency deprecations.
For installation instructions see:
Docker-images are available at:
IOM Helm charts are available at:
For a complete list of all interfaces please see Overview - Intershop Order Management REST API and Overview - IOM Interfaces.