Legacy: Capacity categories

The capacity category allows fulfillment manager to define custom buckets of capacity to be considered during the fulfillment sourcing process. These custom categories are supplied as add ins within the Estimated Delivery Date (EDD) and Checkout API requests.
The primary business value of this legacy feature is the flexibility to define highly customized capacity limits tailored to unique operational workflows. However, this legacy architecture operates strictly as a routing constraint evaluation. It does not possess transactional booking capabilities. Consequently, while the Promising module can evaluate the custom capacity bucket during an availability request, the system cannot securely lock or withhold that capacity during the checkout lifecycle.

Important architecture notice: The legacy capacity category feature detailed on this page is mutually exclusive with the newly introduced Capacity Service. For more information, see Capacity service.
Fulfillment managers and enterprise architects must choose a single approach for capacity management. If you choose to enable the new Capacity Service for end-to-end constraint management and transactional bookings, you cannot utilize the legacy capacity categories.

Legacy API integration

For implementations electing to remain on the legacy capacity category architecture, the following APIs govern the management and retrieval of these custom capacity buckets:

Update available capacity

Configures or updates the capacity availability for a specific custom category. For more information, see putAvailableCapacity API documentation.
List available capacities

Retrieves the current capacity availability metrics for the defined categories. For more information, see listAvailableCapacities API documentation.
Update tags for category

Associates specific inventory or operational tags to a defined capacity category. For more information, see putTagsForCategory API documentation.
Get tags for category

Retrieves the tags currently associated with a specific capacity category. For more information, see getTagsForCategory API documentation.
Delete tags for category

Removes the tag associations from a specific capacity category. For more information, see deleteTagsForCategory API documentation.

If your enterprise requires strict transactional integrity, atomic reservations, and sub second cache lookups, it is highly recommended to migrate your configuration to the new Capacity Service utilizing the standard out of the box fulfillment categories.