APIs

Rank API

The purpose of using Fulfillment Optimizer is to lower the cost to serve while also balancing inventory at the network level. Therefore, it is important that the right set of ship nodes are optimized for a SKU in an order, which is achieved by using the Rank API.

For more information, see Rank API.

Optimizer API

The Optimizer API further optimizes the n ship nodes that are provided by the Rank API. This API accounts for real-time inventory positions and node capacity consumption.

For more information, see Optimizer API.

To understand the difference in the way cost computation is done for the Optimizer API and the Rank API, see Comparing the Rank API and the Optimizer API.

Idle Optimizer API

The Idle Optimizer API enables SmartStart, which allows you to make a preliminary assessment of the benefits of optimization before fully integrating with Fulfillment Optimizer. You can call the API from your order management system when you want to accumulate baseline Key Performance Indicators (KPIs) without configuring any optimization weights within Fulfillment Optimizer. The API request is sent to an internal queue for asynchronous processing. The baseline KPIs are computed after a predefined latency period of approximately 20 minutes. For more information, see Idle Optimizer API.

To understand the differences between the Idle Optimizer API and Optimizer API, see Comparing the Idle Optimizer API and the Optimizer API.

Explainer APIs

When an order is sent to Fulfillment Optimizer, many rules, configurations, and constraints are applied to it to determine the best option for fulfillment. The Explainer APIs provide information about the orders that are processed by Fulfillment Optimizer.]