Enhancements to stage location configuration

Idea Lab

Warehouse teams can now maintain Stage Location Configuration records more efficiently through integrations and APIs, reducing manual configuration effort and supporting faster, more consistent onboarding and maintenance. This enhancement introduces a JSON-based input interface for creating, updating, and deleting configuration records, along with PATCH API support for targeted updates to existing records.

New JSON Input Interface for stage location configuration

A new JSON-based input interface, STAGE_LOCATION_CONFIGURATION, enables users and external systems to submit Stage Location Configuration data in a standardized format. The interface applies record-level validation so that an error with one record does not prevent other valid records in the same interface submission from being processed.

The new interface endpoint is:

.../lgfapi/v10/stage/stage_location_config_intf

The interface supports the following actions:

NOTE: The JSON input includes a header and a stage_location_configuration_list, where individual configuration records and their corresponding action_code are provided. Refer to the applicable interface specification for the supported values for each field.

Synchronous and Asynchronous Processing

The new interface also supports the async parameter, allowing integrations to control how the request is processed.

This provides integrations with greater flexibility when processing Stage Location Configuration data.

PATCH API Support for updating staging location configurations

In addition to the new input interface, LGFAPI now supports PATCH operations for the STAGE_LOCATION_CONFIG entity. Authorized users and integrations can make targeted changes to eligible fields on an existing configuration record without replacing the entire record.

New PATCH endpoint:

PATCH .../wms/lgfapi/v10/entity/stage_location_config/{id}

The following fields can be updated through PATCH:

  • COLUMN_NAME
  • CRITERIA_VALUE

For example, a PATCH request can update the column and criteria values associated with an existing Stage Location Configuration record. PATCH support applies only to existing STAGE_LOCATION_CONFIG records; entity API create and delete operations are not included as part of this enhancement.

Steps to enable and configure

  1. To use these capabilities, you can submit Stage Location Configuration records through the new STAGE_LOCATION_CONFIGURATION JSON input interface and use the async parameter when asynchronous processing is required.
  2. For targeted updates to an existing record, use the new STAGE_LOCATION_CONFIG PATCH API and provide COLUMN_NAME and/or CRITERIA_VALUE as applicable. Standard authorization, validation, and audit controls continue to apply.