Node fulfillment options

When a new order is placed, a specific node is assigned to the order from which the order is shipped. A fulfillment center or a ship node has a predefined fill rate. Unexpected events such as weather and accidents can impact the overall fill rate that results in the delay of the shipment. You can use the Ship Node API's fulfillmentOverrides parameter to turn off a node so that future orders are not assigned to that node. Node fulfillment options are supported at the node level and at the delivery method level.
When you turn off fulfillment at a node, you can also specify an expiry date to determine when to resume fulfillment. The available quantities at the node do not change, but the availability dates change based on the expiry date.
Tip:
  • When you specify an expiry date, ensure that the expiry date is within seven days of the current date.
  • If you do not specify an expiry date, then the node is considered to be off indefinitely.

When fulfillment is off at the node level, all items for this ship node, regardless of segment, unit of measure, or product class, are suspended. When you turn off fulfillment at a delivery method level, all items for this delivery method at the node are suspended. The delivery method level takes higher precedence over the node level. For example, you can turn off fulfillment at a node but override to turn on the PICK delivery method (pick up in store) in that same node. In this scenario, pick up in store is available for all items in that node, but the ship from store is not available. As capacity frees up, you can update fulfillment delivery methods. For example, when capacity resumes higher than 70%, you might want to turn on fulfillment for the SHP delivery method.

For more information, see Update Ship Node.