Optimizer API

The Optimizer API provides optimized ship nodes based on inventory predictive cost estimations by using data to analyze the orders made by customers, products in an order, and type of shipping customers require. The Optimizer API accounts for real-time inventory positions and node capacity consumption and IBM Sterling Fulfillment Optimizer with Watson reduces total cost to serve in real time.

The Optimizer API performs Shadow optimization in addition to regular optimization. KPIs are always computed for the standard optimization and alternate optimization settings. If the sourcing choice of your order management system is passed in the request to the Idle Optimizer API or Optimizer API, the KPIs are computed for the sourcing choice of your order management system.

Accessing the Optimizer API

You can access the Optimizer API from the following URL: 
https://<BaseURL>/<tenantId>/otmz/services/optimizer/V2/<tenantId>

Limitations of the Optimizer API

Consider the following points for the Optimizer API:
  • The OrderDate that is provided to the Optimizer API as input is used for logging purposes. The order is processed with respect to the current time when the order is received by IBM Sterling Fulfillment Optimizer with Watson. A re-sourced order is considered as a new order by Fulfillment Optimizer.
  • Fulfillment Optimizer can process only one ship to address. It uses the address that is provided at order level. If an address is not available at order level, then it uses the address from the first order line.
  • Fulfillment Optimizer cannot process the same SKU if it is part of multiple order lines in the same order.
  • Fulfillment Optimizer can process only one SLA. It uses the value of the attribute CarrierServiceCode provided at first order line.
  • Fulfillment Optimizer does not provided the Cost to Serve information back to the application that is calling the Optimizer API.

For more information about the Optimizer API request and response, see the Optimizer API topic in IBM Developer.