Operative container types

For detailed specifications, refer to the Operative Container Type endpoint in the REST API documentation.

Operative container types provide a structured approach to categorize and handle containers within fulfillment operations, covering the picking, packing, and handover processes. The central container type definition, OperativeContainerType, is utilized across all modules of the platform.

Creating an operative container type

A new operative container type can be created by sending a request to the API.

To enable an operative container type for a specific process, specify the desired operations in the allowedOperativeTypes field. The available values are PICKING, PACKING_TARGET, PACKING_SOURCE, and HANDOVER.

POST https://{YOUR-TENANT-NAME}.api.fulfillmenttools.com/api/operativecontainertypes
{
  "nameLocalized": {
    "de_DE": "Standardbox M",
    "en_US": "Standard Box M"
  },
  "descriptionLocalized": {
    "de_DE": "Eine mittelgroße Box für Standardversand.",
    "en_US": "A medium-sized box for standard shipping."
  },
  "iconUrl": "https://example.com/icon.png",
  "priority": 5,
  "dimensions": {
    "heightInCm": 50,
    "lengthInCm": 100,
    "weightInG": 1700,
    "widthInCm": 25.5
  },
  "weightLimitInG": 2500,
  "allowedOperativeTypes": [
    "PICKING",
    "PACKING_TARGET"
  ],
  "scannableIdentifiers": [
    {
      "searchType": "CONTAINS",
      "identifiers": [
        "BOX-M"
      ]
    }
  ],
  "icon": {
    "content": "<base64-encoded-data>",
    "name": "example.pdf"
  }
}

To use an operative container type in a specific process, specify the desired operations, such as PICKING, PACKING_TARGET, PACKING_SOURCE, and HANDOVER, using the allowedOperativeTypes enumeration.

If the request is successful, a 201 CREATED response is received with a body like this:

Last updated