Feature list
See information about each of the Order Management System (OMS) features, including feature descriptions, availability specifics, and more details, in the tables below.
Authentication | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Authentication - User management | Create new OMS Admin users and assign them specific roles and sources. | No | Yes | No | No |
Authentication - Permission | Define roles with permissions to manage OMS Admin and in-store interface actions. | No | Yes | No | No |
Catalog management | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Catalog management - Catalog maintenance | Automated catalog import info (SKU, main image, product name) via standard message update | Yes | Yes | No | N/A |
Catalog management - Catalog maintenance | Manually request a full catalog export from Magento Commerce. | Yes | N/A | No | N/A |
Catalog management - Catalog maintenance | Automated catalog export, sent to subscribers, triggered by MDC updates of the product message’s required fields | Yes | N/A | No | N/A |
Catalog management - Catalog maintenance | Create products manually via the OMS Admin. | N/A | Yes | No | No |
Catalog management - Product attributes | Import SKUs with identifiers containing blank spaces. | Yes | Yes | No | No |
Catalog management - Product attributes | Support SKU types: Physical (normal physical products w/stock), Service (gift wrap, hemming, engraving, etc.) that can be linked to order or order line, Shipping (shipping type), Virtual (items w/no managed stock or infinite stock), Bundle (products that hold no stock but are grouped to be sourced/shipped together | Yes | Yes | No | N/A |
Catalog management - Product attributes | Record various SKUs for variants of same item. | Yes | Yes | No | N/A |
Catalog management - Services | Record product types as services, which hold no stock info and assumed to always be in stock. For use in customization info (for engraved text, embroidery, warranties, gift wrap etc.) in orders. | Yes | Yes | No | N/A |
Catalog management - Services | Support for gift wrapping options in the catalog associated to a line or at entire order level. | Yes | Yes | No | N/A |
Catalog management - Connector | Select optional attributes to be exported from Magento Commerce catalog. | Yes | N/A | No | N/A |
Customer service | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Customer service - Cancellation | Cancel an entire order not in a logistics or completed status. | Yes | Yes | No | N/A |
Customer service - Return | Create an approved Return Merchandise Authorization for a customer to return their items (incl. info of lines to be returned and reason for return). | Yes | Yes | No | Yes |
Customer service - Return | Cancel an approved Return Merchandise Authorization. | Yes | Yes | No | N/A |
Customer service - Return | Receive full or partial returns and trigger a refund. | Yes | Yes | No | N/A |
Customer service - Return | Accept a return/refund without receiving the returned items if the customer did not receive the item or received a damaged item (customer may send a picture of damage). | Yes | Yes | No | N/A |
Customer service - Return | Specify return reason (wrong size, etc.) for each item received as part of a refund. | Yes | No | No | N/A |
Customer service - Return | Pre-printed return label and return document included in a shipment so customer can efficiently ship the return; Return Merchandise Authorization is created when the initial shipment with all items are shipped (warehouse/store expects all shipped items to be returned), or when the return carrier receives the return label because the customer shipped the return (warehouse/store expects all shipped items from the order that is being returned). | Yes | Yes | No | N/A |
Customer service - Return | The return, optionally incl. return reason and item condition, is directly received in a source (warehouse/store) without Return Merchandise Authorization and triggers a refund | Yes | No | No | N/A |
Customer service - Customer service | Refund shipping costs (no automatic refund) based on configuration: First return - full refund upon received return; Last return - full refund if every line of the order is returned. | N/A | Yes | No | Yes |
Customer service - Exchange | If customer has not received their item, received a wrong item, or received a damaged item, customer service triggers the reshipment, without refund, of an item with the same SKU (shipped if inventory is available) | Yes | Yes | No | N/A |
Customer service - Exchange | Create a new order for a variant of the original order item (expected to be same price), as an exchange, that is linked to the initial order (if it supports returns). | Yes | Yes | No | N/A |
Customer service - Exchange | Customer service can ship an exchange order without receiving a return (“Return with no receiving” feature) if the item is damaged and will be replaced with a new, same or different, item. | Yes | Yes | No | N/A |
Customer service - Reshipment | Initiate the reshipment of previously undelivered item (due to carrier issues). | Yes | Yes | No | N/A |
Customer service - Order display | Discount detail information, incl. promo name and amount, per order line (if supported by frontend provider) | N/A | Yes | No | N/A |
Customer service - Order display | Order traceability list incl. events that affect the order: warehouse communications, payment activities, comments, etc. | N/A | Yes | No | N/A |
Customer service - Appeasement | Apply appeasement on order lines with custom appeasement reason, comment, amount for all items w/valid status to perform action (order must be completed). | Yes | Yes | No | N/A |
Customer service - Order search | Advanced search for order details by order number, customer first name, customer last name, customer email, postal code, etc. | N/A | Yes | No | N/A |
Customer service - Order display | Order shipment details summary incl. tracking info for shipped orders, associated customer sales and service actions, and shipment date of all shipments generated per order | N/A | Yes | No | N/A |
Customer service - Order display | Payment event details per order, incl. type, date/time, total, and status | N/A | Yes | No | N/A |
Customer service - Cancellation | Receive cancellation of orders message from external system for orders not yet sent to the logistics stage. | Yes | Yes | No | N/A |
Customer service - Customer service | Manually refund total or partial shipping costs via an appeasement. | Yes | Yes | No | N/A |
Inventory management | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Inventory management | Centralized inventory info, for selling across sales channels, consolidating warehouse, distribution center, and physical stores sources. | Yes | N/A | Yes | N/A |
Inventory management | Receive and identify stock from multiple sources for dispatch to various channels, fulfilling orders and applying business rules (e.g. single SKU sourced from multiple locations). | Yes | N/A | Yes | N/A |
Inventory management | Calculate available inventory to sell via sales channels. | Yes | N/A | Yes | N/A |
Inventory management | Inventory snapshot of in-flight orders (not sourced or received by warehouse/store) so stock can be decremented appropriately before being exported to the frontend | Yes | N/A | Yes | N/A |
Inventory management | Inventory snapshot indicating the SKUs available per source node and the historical quantity log, indicating who initiated them and when | Yes | Yes | Yes | N/A |
Inventory management | Configure generic safety stock threshold for inventory per source node for calculating stock for sale or export | Yes | N/A | Yes | No |
Inventory management | Report of in-flight stock (cannot be sold online) | Yes | Yes | Yes | N/A |
Inventory management | Safety stock, defined at source or aggregate level | No | Yes | Yes | N/A |
Inventory management | Define safety stock per source for in-store pickup orders | N/A | Yes | No | Yes |
Inventory management | Configure generic safety stock threshold for the catalog at aggregate level so stock exported/available to sell will be deducted accordingly | No | N/A | Yes | N/A |
Inventory management | Stock expert history information incl. creation time and content of the exported message | N/A | Yes | Yes | N/A |
Inventory management | Delta stock updates for all sales channels sharing the same aggregate | Yes | N/A | Yes | N/A |
Inventory management | Manual stock updates per SKU for a specified source, incl. quantity and update reason | Yes | Yes | Yes | N/A |
Inventory management | Configure source node info incl. node name, external ID, pickup location, safety stock quantity, contact details, timezone, latitude/longitude coordinates, supported services, and shipping methods | Yes | Yes | Yes | N/A |
Inventory management | Configure stock aggregates (can have multiple associated source nodes) to be exported to sales channels | Yes | Yes | Yes | No |
Inventory management | Disable stock allocation process to allow external systems to make stock decisions | N/A | N/A | Yes | Yes |
Inventory management | Configure single-aggregate sales channels (for all enabled sources) to receive new orders | Yes | Yes | Yes | No |
Inventory Management | Indicate unlimited stock by SKU/source so OMS will assume constant availability (for virtual goods without quantity limitation or if drop-shipper cannot provide accurate count/guarantees fast replenishment). | Yes | Yes | Yes | N/A |
Monitoring | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Monitoring | Internal 24/7 monitoring for common/critical business rules, providing meaningful info for troubleshooting, to allow visibility to broken processes | N/A | N/A | No | N/A |
Monitoring | 24/7 on-call Account Manager for critical issues | N/A | N/A | No | N/A |
Omnichannel | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Omnichannel - In-store pickup | Web-based application for store associates to manage in-store pickup orders, from picking to collection | N/A | Yes | Yes | N/A |
Omnichannel - Ship from store | Web-based application for store associates to manage ship from store orders, from picking to shipping | N/A | Yes | Yes | N/A |
Omnichannel - In-store pickup | Activate/deactivate sources as pickup locations in the OMS Admin | Yes | Yes | Yes | N/A |
Omnichannel - In-store pickup | Validate active/deactivated pickup locations when orders are imported, and cancel the line for deactivated pickup locations. | N/A | N/A | Yes | N/A |
Omnichannel - In-store pickup | Get updates for new/modified pickup locations in external systems via the API (JSON RPC). | Yes | N/A | Yes | N/A |
Omnichannel - Store fulfillment | Indicate, per-client, pick-decline and customer decline reasons, for use at the order line level, during in-store pickup and ship from store processes. | No | No | Yes | |
Omnichannel - In-store pickup | Split an order to two different stores (in-store pickup available at the line level) during the order create message. | Yes | Yes | Yes | N/A |
Omnichannel - In-store pickup | Record reasons for customer collection decline at the order line level and display in the OMS Admin on Order Overview page and in-store pick list. | Yes | Yes | Yes | Yes |
Omnichannel - In-store pickup | Cancel orders not collected by customer with the Cancel Order button on the in-store pickup pick list page. | Yes | N/A | Yes | N/A |
Omnichannel - In-store pickup | Resource an in-store pickup line, if ship to store is enabled, per client configuration. | N/A | N/A | Yes | Yes |
Omnichannel - In-store pickup | Update order line statuses for in-store pickup shipment requests, via the API, for lines to be collected in-store. | Yes | N/A | Yes | N/A |
Omnichannel - In-store pickup | Configure in-store pickup with specific roles and permissions. | Yes | N/A | Yes | Yes |
Omnichannel - Ship from store | Print a manifest summarizing numbers of to-be-shipped parcels and list them for reference. | Yes | N/A | Yes | Yes |
Omnichannel - Ship from store | Generate a packing slip from a partner/third-party with a link for printing (used as single packing slip or print all the packing slips for a specific pick list). | Yes | N/A | Yes | Yes |
Omnichannel - Ship to store | Order partial in-store pickup and ship to store order,s per independent SKU, for collection in the same store. | No | Yes | Yes | Yes |
Omnichannel - Store fulfillment | Manually select the printer for use via the browser’s printing options. | N/A | N/A | Yes | N/A |
Omnichannel - Printed documents | Pre-print a customer return label and include it in the shipment to/collected by the customer. | Yes | N/A | Yes | Yes |
Omnichannel - Ship from store | Generate a ship from store pick list for a subset of orders per specified parameters or manual selection (for optimal picking and prioritization of urgent orders). | Yes | N/A | Yes | N/A |
Omnichannel - In-store pickup | Process an in-store pickup order paid online or offline (reservation to be paid in-store). | Yes | Yes | Yes | N/A |
Omnichannel - In-store pickup | Add comments (create and customer notes) during in-store pickup picking process. | No | Yes | Yes | N/A |
Omnichannel - In-store pickup | Generate an email order notification and send it to the pick-up location to request fulfillment of the new order. | N/A | Yes | Yes | Yes |
Omnichannel - In-store pickup | Automatically cancel or backorder in-store pickup lines for which stock is not available from pickup location. | N/A | Yes | Yes | Yes |
Omnichannel - Ship from store | Aggregate multiple orders on a pick list (SKUS grouped/managed during pick, pack, and ship process) to optimize the fulfillment process. | N/A | Yes | Yes | N/A |
Omnichannel - Ship from store | Cancel a line during packing process. | N/A | Yes | Yes | N/A |
Omnichannel - In-store pickup | Show product custom attributes from the pick list for in-store pickup orders. | N/A | N/A | Yes | N/A |
Omnichannel - Ship from store | Send an email to the sources address 10 minutes after an executed wave, based on sourcing engine allocation waves configuration, with orders pending pickup info. | N/A | Yes | Yes | N/A |
Omnichannel - Store fulfillment | Display and modify custom attributes of order lines from the pick list for in-store pickup orders or the ship from store orders packing screen. | N/A | N/A | Yes | N/A |
Order processing and fulfillment | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Order processing and fulfillment | Create/update sources with basic details (incl. address and email) via the OMS Admin sources page, .csv file, and standard APIs (JSON RPC), to be used for omnichannel processes and notifications. | Yes | Yes | No | Yes |
Order processing and fulfillment - Source | Upload .csv file containing sources to create/update sources with basic details (address, email) to be used for omnichannel processes and notifications. | Yes | Yes | No | Yes |
Order processing and fulfillment | Breakdown of prices on order lines to be imported/exported incl. prices, discount, VAT, etc.; Payments must be provided at line/item level to facilitate payment operations, such as capture and refund, per part of order (partial shipment, return, refund).. | Yes | Yes | No | N/A |
Order processing and fulfillment | Set statuses at a granular level (order, order line, shipment request level) so that info is tracked at lower levels. | Yes | Yes | No | N/A |
Order processing and fulfillment - Services | Service fee support for order and order line level customizations (engraving, seam, etc.) | Yes | Yes | No | N/A |
Order processing and fulfillment - Services | Support services, such as gift wrap, engraving, etc. (details provided to LSP via shipment request), at order line level. | Yes | Yes | No | N/A |
Order processing and fulfillment - Shipment | Manage multiple shipping addresses (captured on the frontend) per order. Orders with several shipping addresses will be split into several shipment requests. | Yes | Yes | No | Yes |
Order processing and fulfillment -Remorse time | Hold orders, as remorse time, before sending to logistics, so customers can cancel or modify their order before the configurable time period (set by the sales channel). | N/A | N/A | No | Yes |
Order processing and fulfillment | Trigger and send events to a third-party per order status. | Yes | N/A | No | N/A |
Order processing and fulfillment | Configure order flow to be flexible per business needs, such as skipping the fraud check for orders paid w/ Open Invoice, or operating capture before or after shipment, etc. | No | N/A | No | |
Order processing and fulfillment | Import and process products with a pre-shipped status. | Yes | N/A | No | N/A |
Order processing and fulfillment | Integrate with an external source (warehouse, distribution center, store, etc.) via JSON RPC messages (request-_shipment, lines_change_status, lines_shipped, lines_declined) to standard feeds to accelerate warehouse integration. | Yes | Yes | No | Yes |
Order processing and fulfillment | Delivery tracking from international carriers via the LSP to provide delivery info to frontend channels (customer service, online store, etc.) for informing customer about delivery | Yes | Yes | No | Yes |
Order processing and fulfillment - Ship from store | Integrate with carriers to receive tracking details and shipping labels during the ship from store process. | Yes | Yes | Yes | Yes |
Order processing and fulfillment - Shipping | Manage shipping methods on the frontend (defined by the logistics service provider and set up in OMS catalog) and pass it to logistics. | Yes | Yes | Yes | N/A |
Order processing and fulfillment - Shipping | Manage multiple shipping methods per order. | N/A | Yes | Yes | N/A |
Order processing and fulfillment - Shipment | Support multiple shipments, with each shipment triggering events as defined (such as customer notifications), for a single order. | Yes | Yes | Yes | N/A |
Order processing and fulfillment | Receive full or partial order (pre-orders) stock checks showing unavailable items, incl. expected availability date available at the order line level. If, at the time of availability date, there is still no available stock the line is converted to backorder. | Yes | Yes | No | N/A |
Order processing and fulfillment - Source integration | Aggregate lines by SKU and price. | Yes | N/A | No | N/A |
Order processing and fulfillment | Receive full or partial orders (pre-orders) that are not available. When street date/availability date occurs and stock is available the payment is captured and the order is sent to fulfillment. | Yes | Yes | Yes | |
Order processing and fulfillment | Enable backorders to provide a split shipment of available lines and a queue to verify all pending backorders that need to be fulfilled. Additional rules (for instance, “unfulfilled after X days”) will display a high exception. | Yes | Yes | No | Yes |
Order processing and fulfillment | Indicate incoming orders that can be backordered to override the generic backorder acceptance by store. | Yes | Yes | No | Yes |
Order processing and fulfillment | Manually review and cancel list of backorders. | Yes | Yes | No | N/A |
Order processing and fulfillment | Calculate taxes at shipping and reconcile original calculated taxes from checkout. | No | No | No | Yes |
Payment | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Payment - Offline | Process orders and refunds that are managed/paid offline. | Yes | Yes | Yes | N/A |
Payment | Settlement/capture request to gateway provider. | Yes | N/A | No | N/A |
Payment | Refund tender correctly (PayPal, BrainTree, CustomPayments) per post-sales actions (returns, appeasements, etc.). If offline, refunds are managed by the partner. | Yes | N/A | No | N/A |
Payment | Cancel authorization if the order is canceled. | Yes | Yes | No | N/A |
Payment | Track payment events (authorization, validation, settlement refund) per order. | Yes | No | No | Yes |
Payment | Request capture of all shipped lines before or after daily scheduled capture. Shipping fees are captured per client configuration, with first or last shipment. | Yes | N/A | No | Yes |
Release process | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Release process | Execute automated and regression test release process in continuous integration environment. | N/A | N/A | No | N/A |
Release process | Provide distinct staging and production environment(s). | N/A | N/A | No | N/A |
Reporting | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Reporting | Easily modify the full dashboard date range for reports instead of using the default date range. | N/A | N/A | No | N/A |
Reporting | Dashboard showing all OMS orders | N/A | N/A | No | N/A |
Reporting | Dashboard showing all shipped OMS orders | N/A | N/A | No | N/A |
Reporting | Dashboard showing all canceled OMS orders | N/A | N/A | No | N/A |
Sourcing | Feature description | External message | OMS Admin | Store fulfillment module | Config system |
---|---|---|---|---|---|
Sourcing | Configure direct/batch sourcing modes (sourced first-in/first-out to determine best option) for home delivery. Orders are batched in a queue to allow accumulation of data for sourcing from optimal node, and to optimize the use of source stock across requests to ensure priority options are sourced successfully and shipments/backorders are minimized. | Yes | Yes | Yes | |
Sourcing | Direct sourcing for in-store pickup orders to ensure fast order preparation and customer collection | Yes | N/A | No | |
Sourcing | Direct sourcing, in batch mode, for backordered/declined lines | Yes | N/A | No | |
Sourcing | Configure specific sources to be ignored during allocation wave | N/A | N/A | Yes | |
Sourcing | Sourcing request on a SKU, for a specified delivery address, before order creation (best option provided in an asynchronous response) | Yes | No | N/A | |
Sourcing | Generate sourcing options and scoring via a “search tree”, which explores all possible options, based on customer restrictions, for the next successive line in the order. Each option is scored, from 10.0 (best) to 0.0 (worst), with the best option returned as the ideal sourcing response. Info for all scored options for a given order available in the OMS Admin. | N/A | Yes | Yes | |
Sourcing | Configure scoring rule weights, by numeric value, to determine the weight that is used to define the final scored options. | N/A | N/A | Yes | |
Sourcing | The sourcing engine, configured based on age, shipping method, and request size (line count), allows batch sorting to minimize splits (sort by request size, shipping method, age) and ensure timely shipping (sort by age, size, shipping method). | N/A | N/A | Yes | |
Sourcing | Weighted rules (balanced via scored options) allow for the minimization of splits. | N/A | N/A | Yes | |
Sourcing | Weighted rules (balanced via scored options) prioritize sources based on source ranking. | N/A | N/A | Yes | |
Sourcing | Weighted rules (balanced via scored options) prioritize sources based on stock availability. | N/A | N/A | Yes | |
Sourcing | Weighted rules (balanced via scored options) prioritize sources based on source distance from delivery address. | N/A | N/A | Yes | |
Sourcing | Configure rule to determine maximum splits allowed per sourcing request of an order. If a limit is defined it will be accounted for separately in each allocation wave (previous runs with a generated split are not accounted for). | N/A | N/A | Yes | |
Sourcing | Configure rule to avoid partial order sourcing (if some lines do not have stock), holding back the entire order as a backorder instead. | N/A | N/A | Yes | |
Sourcing | Configure rule to ensure all bundles lines are sourced together to same source. | Yes | Yes | ||
Sourcing | Configure rule to allow bundle splitting after reaching a threshold of failed attempts to source the request (bundle must be completely sourced). | N/A | Yes | ||
Sourcing | Calculate the GPS coordinates of the shipping address via the Google Maps API to store for the predetermination of shipping distance to available sources. | N/A | N/A | Yes | |
Sourcing | Configure rule to filter sources by required services per source so that service-included orders can be exclusively routed to the appropriate sources. | Yes | N/A | No | |
Sourcing | Configure rule to filter sources by shipping method type per source so orders can be exclusively routed to the appropriate sources. | Yes | N/A | No | |
Sourcing | Configure rule to filter sources by shipping zone so orders can be sourced only to sources in the same zone (defined by country or state mapping). | Yes | N/A | Yes | |
Sourcing | Configure rule to allow ship from store pick-declined orders to be re-sourced automatically during the next configured allocation wave, or canceled. | N/A | N/A | Yes | |
Sourcing | Configure rule to allow un-picked orders in the allocation queue to be re-sourced (only orders not hard allocated to store type sources) to the best available source in the next allocation wave. | N/A | N/A | Yes | |
Sourcing | Configure rule to specify the minimum time an order is hard allocated to a store before being re-sourced. | N/A | N/A | Yes | |
Sourcing | Configure rule to allow pick-declined in-store pickup orders be moved to the manual queue for manual sourcing or cancellation. | N/A | N/A | Yes | |
Sourcing | Configure rule to discard sources that pick-declined a home delivery order so they will not be similarly sourced again. | N/A | N/A | Yes | |
Sourcing | Manually decide order line allocation of orders (not hard allocated/still in the sourcing queue) to specified sources that have available stock and are part of the stock aggregate. | N/A | N/A | N/A | |
Sourcing | Define a source per order line level to be used for order sourcing (if no stock is available/order line will be backordered). | Yes | N/A | N/A | |
Sourcing | Queue of orders pending sourcing (backorders, orders not sourced because of rule limitations) sorted by order age, that allows manual forcing of a sourcing decision or order cancellation. | No | Yes | N/A | |
Sourcing | Sourcing history for each possible order, incl. available stock in the source, selected per sourcing wave, and a reasons list for orders that cannot be sourced | Yes | Yes | N/A | |
Sourcing | Configure shipping method time-frames to flag an order as an overdue exception. | No | Yes | Yes | |
Sourcing | Configure backorder time-frames to flag an overdue exception (aged backorder) when time expires. | No | Yes | Yes | |
Sourcing | Configure a list of allocation wave (applies to orders queued in batch, backorders, or un-sourceable orders modes) time sets to determine scheduling for sourcing queue orders to be processed. | No | No | Yes | |
Sourcing | Source an order (ship to store capability) that has a pickup location but unavailable stock. The engine searches for most appropriate source with ship to store capability (able to be shipped to any provided pickup location). | Yes | N/A | Yes | |
Sourcing | Receive an in-store pickup order with a predefined source location (per order line) to determine which source will provide stock to the final pickup location. If stock is available at pickup location the source location field is ignored. | Yes | N/A | N/A | |
Sourcing | List of sourcing options per order that will be scored during the wave, incl. final ranking info | Yes | Yes | N/A | |
Sourcing | Fulfill split orders (items from different sources) per stock availability via client rules decided by the sourcing engine. | Yes | Yes | Yes | N/A |