Resource pool

The Resource pool serves as the central execution profile that seamlessly integrates all capacity components. It links the service category, the operation calendar, and the capacity unit of measure to a specific fulfillment node into one cohesive operational entity.

Resource pool types

To assist fulfillment manager in managing complex enterprise networks, the resourcePoolType attribute differentiates the core purpose of the resource pool. Supported values include:
  • PROD for standard product fulfillment.
  • CARRIER_SERVICE for outbound logistics tracking.
This classification allows users to filter and identify specific operational constraints across the network.

Capacity unit of measure option

Once defined, the capacity units consumed per order are strictly dictated by the unit of measure bound to the resource pool. The primary consumption metrics include:
  • UNIT
    Represents the individual item quantity presented in the order. For example, an order containing two items quantity consumes two units of capacity availability.
  • RELEASE
    Represents the consolidated number of packages fulfilled or leaving the facility regardless of the item quantity. For example, if the promising checkout estimate determines that an order requires two separate packages for shipment, then exactly two units of capacity availability will be consumed even if the order line quantity is 5.

Auto-discovery execution

After the resource pool is configured, the system automatically computes capacity availability based on the linked operation calendar slots and their corresponding capacity components described above. The auto discovery feature activates immediately based on the associated service category subscriptions. This intelligent routing eliminates the need for the fulfillment manager or the upstream commerce application to explicitly track, remember, or transmit the exact resource pool identifier during checkout or estimation requests.

During promising estimated delivery request, if a resource pool is not found for specific service category, then the capacity is untracked or capacity is infinite.
Note: Custom resource pool configurations are not yet supported in Sterling Intelligent Promising.

Example configuration payload

Below is a sample payload illustrating a standard resource pool definition:
{
  "node": "DC_ALABAMA",
  "resourcePoolId": "DC_ALABAMA_FULFILLMENT_RESOURCE_POOL",
  "unitOfMeasure": "LINE",
  "categorySubscriptions": [
    "STANDARD_PRODUCT_CAPACITY"
  ],
  "calendarId": "DC_WORKFORCE_SCHEDULE",
  "description": "Fulfillment Resource Pool",
  "resourcePoolType": "PROD"
}
For more information, see ResourcePool API.