Packing

Pack jobs are designed to pack already picked items into to boxes or bags. In addition, documents can be printed and added to the parcel. This part is especially relevant for ship-from-store orders as usually shipping labels and other documents are printed and added to the parcels here. Once orders are packed, they typically are stored for handover.

Packing container types

Packing containers represent physical containers in which picked items are packed for the handover. For example, packages for shipping orders or bags that are handed over to a customer in a store. When creating a packing container one of the preconfigured packing container types must be chosen.

• Packing container types handle:

  • name, description & icon

  • dimensions (optional)

  • maximum weight packing container can carry (optional)

Packing configuration

In the packing configuration users can define:

• the scanning type for pack line items

• if packing containers are required

• if pack line items need a confirmation

• if packing source containers are used

Please go to the Developer Docs for more information on the packing configuration. A packing REST API documentation is available too.

Scanning type

The scanning type defines whether a physical scan of the code of all pack line items is required in order to finish a pack job.

The available options are: SCAN_NOT_REQUIRED or MUST_SCAN_EACH.

SCAN_NOT_REQUIRED: a scan is not needed MUST_SCAN_EACH: each pack line item has to be scanned

Packing container required

This configuration enables the search for pack jobs via the scanned code of load units. If set to true, the search is available in the pack job screen, if set to false, the search is not available

Packing item confirmation needed

This configuration activates the need to check each pack line item within a pack job in order to finish a pack job. If set to true, each pick line item needs to be checked off, if set to false, checking off is not needed in order to finish a pack job.

This config will have no effect when scanning type is set to MUST_SCAN_EACH. In this case scanning each pack line item is mandatory in order to finish a pack job.

Packing source container configuration

This configuration enables the creation of packing source containers. Packing source containers contain one or more items for a pack job. This can be, for example, a load unit.

If set to true, packing source container are created from existing load units when a pack job is created from a pick job. If set to false, packing source container are not created as explained in the previous sentence.

In order to be able to search for pack jobs via the scanned code of a load unit packing packingContainerRequiredConfiguration as well as packingSourceContainerConfiguration have to be set to true.

Operative container types

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:

{
  "id": "5f09e57b-571a-45d9-96bd-020308275dd6",
  "name":"Standardbox M",
  "nameLocalized": {
    "de_DE": "Standardbox M",
    "en_US": "Standard Box M"
  },
  "description": "Eine mittelgroße Box für Standardversand.",
  "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": {},
  "weightLimitInG": 500,
  "iconUrl": "https://cdn-icons-png.flaticon.com/512/1380/1380641.png",
  "allowedOperativeTypes": [
    "PICKING",
    "PACKING_TARGET"
  ],
  "scannableIdentifiers": [
    {
      "identifiers": [
        "BOX-M"
      ],
      "searchType": "CONTAINS"
    }
  ],
  "customAttributes": {},
  "version": 1,
  "lastModified": "2025-06-04T15:35:29.659Z",
  "created": "2025-06-04T15:35:29.659Z"
}

To enable the packing process in the Operations App, the allowedOperativeTypes field must include PACKING_TARGET.