Comparing the Rank API and the Optimizer API
The computation for the Optimizer API and the Rank API is different in nature.
Use the Optimizer API to further optimize the top n ship nodes provided by the
Rank API. The Optimizer API accounts for real-time inventory positions and node capacity
consumption.
The Rank API processes a large set of ship nodes that are ranked based on SKU inventory position and cost. The Rank API computes the total cost considering shipping cost, capacity cost, and processing cost for ship nodes of each item.
The Rank API processes a large set of ship nodes to be ranked based on
SKU inventory position and cost. The Rank API computes total cost considering shipping cost,
capacity cost, processing cost, stock-out avoidance cost and markdown avoidance cost for ship nodes
of each item. Some of these costs are calculated offline.
| Subject | Optimizer API | Rank API |
|---|---|---|
| Shipping cost | Cost is calculated by using Transit Rates that is defined for carrier services. Optimizer API considers all carrier services, which are mapped to the ship node and can meet the Days to deliver criteria. | Cost is calculated by using Transit Rates that are defined for carrier services. The Rank API considers one carrier service, which is cheapest for the weight of Order Line. |
| Capacity cost | Cumulative Capacity Utilization (CCU) is calculated at run time by using capacity that is consumed for a ship node. Cost is calculated by applying node balancing coefficients to CCU. | The CCU calculation is not done at run time. The latest CCU value for a ship node, which is calculated by the Optimizer API is cached and used. Cost is calculated by applying node balancing coefficients to CCU. |
| Processing cost | Cost is calculated by using Processing Cost configuration data with quantity on assignment. | Cost is calculated by using processing cost configuration data with the quantity on an order line. |
| Stock out avoidance cost |
Cost is calculated in real time for SKU using available inventory, velocity, quantity assigned, and value at a ship node. | Cost is calculated by a separate, offline process for an SKU. The process uses available inventory, velocity, and value at a ship node for 1 unit of SKU. Offline cost is multiplied with the requested quantity on an order line. |
| Markdown avoidance cost |
Cost is calculated in real time for SKU using available inventory, velocity, quantity assigned, online price, markdown price, and markdown date at a ship node. | Cost is calculated by a separate, offline process for an SKU. This process uses available inventory, velocity, quantity assigned, online price, markdown price, and markdown date at a ship node for 1 unit of SKU. Offline cost is multiplied with the requested quantity on the order line. |
| Optimizing orders with vendor (direct ship-to vendor) nodes | Handles order lines with vendor nodes. For more information, see the Optimizing orders with vendor (direct ship-to vendor) nodes section in the Request and response for Optimizer API and Idle API topic. | Does not complete any specific handling for order lines with vendor nodes. |