Zone picking

This page is outdated. Please go to our new documentation under https://docs.fulfillmenttools.com/documentation.

It is currently possible to use our first version of zone picking on our platform. On this page all available options are described.

Creating zones

By using POST call at /api/facilities/:facilityId/zones it is possible to create zones easily for each facility:

{
  "name": "Name of the zone",
  "score": 0
}

Assigning users to a facility

By using POST or PATCH call at /api/users/:userId each user can carry at least one zone. After a zone is created, it can be assigned to any available user. Assigned zones must be given in context of assigned facilities:

{
    "version": 1,
    "actions": [
        {
            "action": "ModifyUser",
    "assignedFacilities": [
        {
            "facilityRef": "a16dcc81-c16f-4bd5-bbcd-375a42dfd2c5",
            "assignedZones": [
                {
                    "zoneRef": "93cfae89-08c7-46bf-8eb0-c91dc836fdf2"
                },
                                {
                    "zoneRef": "cd059486-4b35-4e4a-a172-8dcb85e2d792"
                }
            ],
            "id": "ca996568-9a6c-4538-a10d-eba16c7cac35"
        }
    ]
        }
    ]
}

Assigning storage locations to zones

For a user to be able to pick products from a specific zone, those products need to be linked to that zone. Currently, this linkage can only be achieved through the use of storage locations that have an associated zone. Consequently, products located in these storage areas will be automatically assigned to the respective zone.

By using PUT or POST at /api/facilities/:facilityId/storagelocations/:storageLocationId the zone can be assigned to a storage location.

{
  "version": 1,
  "tenantLocationId": "S4",
  "name": "S4",
  "type": "SINGLE_STORAGE",
  "runningSequences": [
  ],
  "scannableCodes": [],
  "zoneRef": "ID-OF-THE-ZONE-THE-SL-BELONGS-TO",
  "traits": ["PICKABLE"]
}

How to create a picking task with products in zones

Upon the zone's creation and its assignment to both a zone and storage locations, it becomes feasible to generate picking tasks that can be executed by users assigned to that particular zone.

This can be achieved by creating a picking task that includes a tenantArticleId associated with a storage location that has a designated zone. As a result, this newly created picking task will be automatically allocated to that specific zone.

How does that effect the visibility of a picking task when it needs to be picked within a zone?

Example: Zones A, B and C are available in the facility Picker is assigned to zone A and B.

1. Pickjob with Zone A and B => picking task is pickable

2. Pickjob with zone A, B and C => picking task is pickable

3. Pickjob with zone C => picking task is not pickable

4. Pickjob with zone B and C => picking task is pickable

When a user doesn’t have any zones assigned, they see every picking task

How do notifications for zones work?

Notifications also function at the zone level. Whenever a picking task becomes available for a user within their assigned zone, they will receive a notification. However, if the picking task is not accessible to the user within their assigned zone, no notification will be received.

How can a picking task receive a zone?

Presently, the picking task gets automatically assigned to a zone immediately after a product is allocated to a storage location within that zone.

Can other tasks can handle zones?

Not yet. This will be added to our product soon.

Is it possible to divide a picking task into various segments when allocated products need to be assigned to different zones?

Not yet. This will be added to our product soon.