Order Search
Whenever an order is modified in Sterling Order Management System Software, save an outline of an order in Order Search so that the latest state of an order is always available in Order Search. Order Search also provides the capability to index selected contents of the outline such as commonly used searchable fields, fields that require sorting, and so on so that a wide range of search and faster retrieval are possible.
To store an order outline, Order Search uses
Elasticsearch (ES), which is a Lucene-based indexing solution. The order outline schema is mapped to
an order index schema by using the mapping features from ES, and an index is created with the schema
in ES. When an order outline document is sent to Order
Search, an order index document is derived from the outline and stored against a unique
identifier in ES. Each order index document consists some internal fields, that are defined for
various purposes. One such field is status
. This field conveys whether an order is in
Sterling Order Management System Software or Archive Service. When you archive an order from
Sterling Order Management System Software, the corresponding order document status in Order Search is marked as archived
and the order is removed
from Sterling Order Management System Software. If you want to retrieve more details beyond order outline,
Archive Service can fulfill this requirement by calling the retrieve APIs.
The order outline that is sent to Order Search mostly consists of searchable contents of an order such as bill to ID, shopper name, phone number, address, email, item information, and any other information pertaining to the order and related data to feed an e-commerce application or list user interfaces (UIs) in Sterling Order Management System Software. These UIs does not require a detailed information, and hence it can be filled from the outline data present in Order Search. The need to fetch order data from Sterling Order Management System Software or Archive Service arrives only when you need more information.
After an order is confirmed, most of the searchable fields in the order outline data are unlikely to change, thus reducing the number of save attempts. To further reduce the save attempts, disable the save operation when an order is transient. For example, an order in draft status (cart is not closed) is more prone to changes. To avoid multiple propagation to Order Search, you can disable the draft save operation.