Release notes for OMS

These release notes document numerous functional fixes and enhancements of the Order Management System. Release notes are published in conjunction with the release to staging, approximately one week before the production release.

To see release notes specifically for hotfixes, check out Hotfixes.

Release notes include:

  • New features
  • Improvements
  • Known issues


Staging release—June 4, 2019

Production release—June 12, 2019

  • Recommended limit of order lines that can be correctly processed—The recommended number of order lines is 200 lines per order. See the FAQ page for more information.

  • Order creation date available in the Backoffice export—The order export functionality in the Backoffice now exports the order_creation_date attribute.

  • Maximum number of characters allowed in the product_name field increased—This fix allows the product_name description field on the order.create message to be updated from 300 to a maximum of 1000 characters.

  • shipment_date allowed when shipment_done event is triggered—Now, there is a shipment_date event available when the customer_shipment_done is triggered.


Staging release—May 7, 2019

Production release—May 21, 2019

  • Loader shows progress of mass actions—We have implemented a visual loader to indicate the status of the batch operation, or mass action, during the picking and collection processes.


Staging release—April 9, 2019

Production release—April 16, 2019

  • Expanded Manual Actions functionality—Users with roles restricted by Sales Channel can now access the Manual Actions tab for a specific order in the OMS Backoffice.

  • Decline collection of all items—We added the ability to decline the collection of all lines and items of an ISPU bulk pick list.

  • Decline picking of all items—We added the ability to decline the picking of all lines and items of an ISPU bulk pick list.

  • Confirm Picking and Decline Picking options—Availability of new Confirm Picking and Decline Picking options when confirming or declining ISPU orders and Confirm Collection and Decline Collection options when confirming or declining customer collection.

  • Show number of items in pick list—Now you can see the total number of items in the pick list.

  • Decline reason in Customer Collection View—We have added the ability to select the decline reason in the Customer Collection view for declined lines of an ISPU bulk pick list.

  • Confirm/decline collection of multiple items—Store assistants can now Confirm & Collect or Decline the collection of multiples lines of an ISPU pick list in the Customer Collection view.

  • Confirm/decline collection of all items—Store assistants can now Confirm & Collect or Decline the collection of all lines of an ISPU pick list in the Customer Collection view.

  • Select decline reason in PickList view—Store assistants can now select the decline reason of selected lines of an ISPU bulk pick list.

  • Confirm/decline picking of multiple items—Store assistants can now confirm and decline multiple items of selected lines of an ISPU bulk pick list.

  • Confirm picking of all items—Store assistants can now confirm all lines of an ISPU bulk pick list.

  • Improved custom attributes modification—The process of modifying customer attributes has been greatly improved with the addition of a dropdown menu showing valid values for selection, including supported attribute types and associated validations, and modifiable entities.

  • Re-trigger payment capture—In a payment capture exception, you now have the ability to re-trigger the payment capture to recover captures during a payment integration outage or other similar event.

  • Inflight stock info available at source level—To ensure the most up-to-date info for available stock per source, information about inflight stock is available at the source level to the broadcasted event via the source_stock_management.updated message.


Staging release—March 12, 2019

Production release—March 19, 2019

  • Implement feedback banner in Magento Admin—To gather helpful feedback from users/clients, we have implemented a feedback banner in the Magento Admin requesting information from users about the system’s capabilities and functionality.

  • Add shipment date in order view—The shipment date for an order is now visible in the order view for Shipment Requests and Shipments.

  • Dashboard to display exceptions—The dashboard will provide users, with the appropriate permissions, visibility to pending payment issues.

  • Revise user configuration template—The previous configuration option for adding new users in the CSV template file for user creation, “access_all_sales_channels_and_sources”, was removed from the CSV template so that only current functionality and options are visible.

  • Provide notification for payment event failure—Payment events failures will now generate a magento.common.error_management.notify message to allow the System Integrators (SIs) to understand which events were not correctly processed by the OMS.

  • Custom attributes search usability improvements—We improved the usability of the custom attributes search field. Values are shown in a dropdown menu to assist in properly filling in this field.

  • Add the custom attribute type URL—Now you can define a custom attribute as a URL to access an external source.

  • Custom attributes showing properly in the In Store Pickup page—Custom attributes are now properly visible in the In-store Pickup Magento Admin page.

  • Order ingestion validations—Custom attributes are now received with matching definitions, defined by the business, so that if you receive invalid data you can prevent any corrupted data coming from integrations like ERP or CRM.


Staging release—February 12, 2019

Production release—February 19, 2019

  • Promotional info added to shipment request message—Line level promotional information was added to the magento.logistics.warehouse_management.request_shipment message.

  • Configure order attributes visibility in Sales grids—You can now configure which custom order attributes are visible on some Sales grids in Backoffice (Sales, Customer service, and ISPU). The newly configured customer order attribute columns will be saved in your user profile, and are visible when you log back in.

  • Custom attributes and promise delivery date added to sourcing request—Custom attributes prefixed with mom_srcrr_ and the promise delivery date have been added to the sourcing request, so that you can overwrite specific sourcing rules via custom attributes provided in the order and source orders by promise date.

  • Access to manual order actions—New comprehensive user and roles functionality now provides the ability to perform manual actions for an order.

  • Support bundles with multiple quantities—We now support bundles with multiple quantities via the parent_line_number field in the order create message, which allows you to provide definition of the parent/child relationship. The parent_line_id field is now deprecated.

  • Generate a payment ingestion failure message—A message will be generated each time a payment event fails to be ingested by the OMS, and will provide helpful information for troubleshooting the integration or other issues, via the magento.common.error_management specification.

  • agedBackorders sourced at same time—Now, instead of submitting orders in the sourcing wave every X hours when stock is received in the warehouse/source, the stock snapshot is used to validate which of the agedBackorders received stock. Then the agedBackorders be re-queued for the next allocation wave (same day).

  • Information is searchable by sales channel—You can search for information per sales channel with the optional (for search fields and response) sales_channel_id in the command.


Staging release—January 14, 2019

Production release—January 23, 2019

  • Overwrite bundle sourcing rule—You can now overwrite the bundle sourcing rule at the order level using a custom attribute.

  • Define order-specific sourcing override rules—You can now overwrite the generic order configuration to treat single-shipment orders as split orders if stock is available in different sources, but should not be partially sourced due to stock availability or rule limitations.