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 the Optimization service 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.

If in case, the carrier services are predefined and preferred delivery method is ship, a fulfillment manager can input Carrier Service IDs in the preferredCarrierServices field. You can input Carrier Service IDs at either order level or order line level. This enables the Optimization service to consider the preferred carrier services over other carrier services within the specified shipping groups.

Note: For the Optimization service to consider the preferred carrier services, it is important that a fulfillment manager adds those carrier services as members of the specified shipping groups.

Accessing the Optimizer API

You can access the Optimizer API from the following URL:
https://<BaseURL>/optimizer/{tenantId}/v3/order/optimization

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 the Optimization service. A re-sourced order is considered as a new order by the Optimization service.
  • The Optimization service 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.
  • The Optimization service cannot process the same SKU if it is part of multiple order lines in the same order.
  • The Optimization service can process only one SLA. It uses the value of the attribute CarrierServiceCode provided at the first order line.
  • The Optimization service does not provide the Cost to Serve information back to the application that is calling the Optimizer API.