fulfillmenttools
  • Welcome to the fulfillmenttools Platform Documentation
  • Getting Started
    • Setup your access to fulfillmenttools
    • Make your first API Calls
      • Add your first facility
      • Add your first listing
      • Place your first order
    • Core concepts & terminology
      • Order Flow
    • Postman Collection
    • Client SDKs
    • FAQ
  • Clients
    • Backoffice
      • First steps - Registration
      • Network view
        • Home
        • Orders
          • Unroutable orders
          • Pre-orders & Backorders
          • Order History
        • Inventory Management
          • Stock Overview
          • Channel Inventory
        • Facilities
        • Users
        • Returns
        • DOMS configuration
        • Settings
        • Analytics
          • DOMS Pages
          • Fulfillment Operations Pages
          • Inventory Pages
          • Downloads Page
      • Facility view
        • Home
        • Inbound
        • Tasks
        • Listings
        • Storage Locations
        • Facility
        • Users
    • Inventory app
      • Registration Inventory App
      • App sections
        • Inbound
        • Storage and relocation
    • Operations app
      • Android
        • Manual Registration
        • Android Enterprise Registration
        • Sections
          • Picking
            • Load Units (legacy)
            • Substitute items
            • Weighed or measured products
            • Scanning configuration
            • Picking Methods
              • Batch Picking
              • Multi Order Picking
          • Packing
          • Handover
          • Returns (legacy)
        • Printing
        • Notifications
      • Webapp
        • Packing
      • Overview features Android & Webapp
    • Technical requirements
      • Zebra Hardware Scanner Configuration
      • Honeywell Hardware Scanner Configuration
      • Supported barcodes for camera scanning
      • Requirements for fft applications
      • Zebra printer
    • Returns app
      • Handle unannounced returns
      • Handle announced returns
  • Products
    • Core Functionality
      • Process
        • External actions
      • Add and manage facilities
      • Notification Center
      • Checking on features
      • Tags and Stickers Concept
      • GDPR
      • Remote Configuration
      • Expiry
      • Target time
      • Time calculation for queries of future availabilities (LPS-calculation)
      • Interfacility Transfer
    • Carrier Management
      • Overview
        • Available Carriers
      • Concepts
        • Carrier Country Service Mapping (CCSM)
        • Non-delivery-days
        • Custom Carrier & Headless operation of Carriers
      • Providing needed data
    • Fulfillment Options
      • Fulfillability Check
      • Checkout Options
        • Available fulfillment options based on basket
        • Earliest possible delivery date
        • Available delivery dates within time-period
        • Availability for delivery date
      • Delivery Promise
    • Inventory Management
      • Configurations
      • Entities
        • Listing
        • Stock
          • Stock Properties
        • Storage Location
        • Zone
      • Global Inventory
        • Stock availability
        • Channel Inventory
        • Expected stock
        • Inbound Process
        • Reservations
        • Safety Stock
      • Inventory Control
        • Inventory Traits
        • Measurement Units
        • Outbound Inventory Tracking
        • Storage Location Recommendations
    • Order Fulfillment
      • Headless Order Fulfillment
      • Pick Jobs
      • Zone picking
      • Load Units
      • Custom Service
      • Handover Jobs
      • Add External Documents
      • Configurations
        • Picking Configuration
          • Picking methods
          • Short Pick Reasons
        • Packing Configuration
          • Packing Container Types
        • Print / Document Configuration
        • Tag Configurations
          • Parcel Tag Configuration
        • Handover Configuration
        • Operative Container Types
    • Order Routing
      • Entities
        • Ship-from-Store Orders
        • Click-and-Collect Orders
        • Locked Orders
        • Custom Services Orders
          • Simple Custom Service Order
          • Complex Custom Service Order
      • Fences
      • Ratings
      • Order Split
        • Order split - initial routing
        • Order split after shortpick
        • Item bundles
      • Reroute
      • Shape the routing with the DOMS Toolkit
      • Decision logs
    • Returns Management
      • Returns legacy
        • Available status
      • Returns 2.0
        • Return Reasons
        • Item Conditions
        • Integrating Returns with Events
    • Use Cases
      • Demand-Driven Replenishment
      • Expected stock in availability
      • Multi Order Picking
      • Interfacility transfer
      • Assigned Users
  • Connecting to fulfillmenttools
    • General Topics
      • Use external identity providers to authenticate to fulfillmenttools
        • Microsoft Entra ID / Azure Active Directory (AD)
      • Public Event Export
      • Available Regions
      • Backup Policies
    • GraphQL API
    • RESTful API
      • General Topics
        • API Release Life Cycle
        • Versioning
        • Authorization
        • Customization via Attributes
        • Update Guarantees
        • Rate Limits
        • Resource Timestamps
        • Pagination Interface
        • Localization
        • Custom Attributes
      • OpenAPI Specification
        • Swagger UI
        • OpenAPI 3.0 Spec
    • Eventing
      • Structure of an Event
      • Available Events
      • Tutorial
    • commercetools Connect
    • Integration Tutorial
      • Adding facilities
      • Adding listings to facilities
      • Configuring stocks
      • Carrier configuration
      • Placing orders
      • Checkout Options
      • Distributed Order Management System (Routing)
      • Local fulfillment configuration
  • Incident Reporting
    • How to report incidents in fulfillmenttools
    • How to define incident priorities
  • Release Notes
    • Release Summary – May 2024
    • Release Summary – June 2024
    • Release Summary – July 2024
    • Release Summary – August 2024
    • Release Summary – September 2024
    • Release Summary – October 2024
Powered by GitBook
On this page
  • Introduction
  • Configuration
  • Setting tenant wide default picking method
  • Configuration of picking methods in a facility
  • Configuration of the preferred picking method in a pickjob

Was this helpful?

  1. Clients
  2. Operations app
  3. Android
  4. Sections
  5. Picking
  6. Picking Methods

Batch Picking

This page describes batch picking and how to configure it.

PreviousPicking MethodsNextMulti Order Picking

Last updated 5 months ago

Was this helpful?

This page is outdated. Please go to our new documentation under .

Introduction

Batch picking is one of the available multi order pick methods of fulfillmenttools. A pick run combines multiple pickjobs which represent parts of or a whole consumer order. When two pickjobs of a batch pick run contain the same article, the two articles are merged to one pick line item for the picker.

Please see the following example: Pickjob A contains the item "apple" with a quantity of 3. Pickjob B contains article "apple" with a quantity of 5. A batch pick run of these two pickjobs would combine both pickjobs and results in three pick line items in the pickrun - one of them is "apple" with a quantity of 8.

After the pick process is finished the picked items are distributed into order specific batches of goods again to be shipped or handed over.

Configuration

Wether a single order can be part of a batch pick is depended on three configurations with different priorities. The configuration is done on three levels, namely:

The three levels of configuration are, as mentioned above, partially superseding, which means in this case: When a pickjob is marked as one, that should be fulfilled by a Batch Picking process, it overrules any configuration given to the facility or the tenant.

Setting tenant wide default picking method

The PATCH method on the /api/configurations/picking endpoint can be used to change the value:

curl --location --request PATCH 'https://your.api.fulfillmenttools.com/api/configurations/picking' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '{
    "version":25,
    "pickingMethodsConfiguration": {
        "defaultPickingMethod": "BATCH"
    }
}'

Configuration of picking methods in a facility

curl --location --request PATCH 'https://your.api.fulfillmenttools.com/api/facilities/0a3fe1dd-70d8-43b3-a70a-2cff78a4d439' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '{
    "actions": [ 
        {
            "action":"ModifyFacility",
            "pickingMethods": ["BATCH"]
        }
    ],
    "version":20
}'

200 OK
{
    "name": "Store Cologne",
    "pickingMethods": [
        "BATCH"
    ],
    ...
}

Configuration of the preferred picking method in a pickjob

To keep things easy a pickjob knows about the desired picking methods. The value is written to the pickjob itself (field preferredPickingMethods). The value here is the outcome of any given configuration on tenant or facility level and may be overwritten during creation of the pickjob.

Be aware: Providing pickingMethods in the creation of a pickjob might overwrite any given facility specific or tenant wide configuration.

Configure picking methods via Tags

It is also possible to add picking methods according to present tags on the pickjob. Please see the following issued configuration:

curl --location --request PUT 'https://your.api.fulfillmenttools.com/api/configurations/tags/pickjob' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '{
    "preferredPickingMethodsConfiguration": {
        "preferredPickingMethodsPerTag": [
            {
                "tagRef": "Consumer Group",
                "matchingValues": [
                    "B2C"
                ],
                "pickingMethods": [
                    "BATCH"
                ]
            },
            {
                "tagRef": "Consumer Group",
                "matchingValues": [
                    "B2B"
                ],
                "pickingMethods": [
                    "SINGLE_ORDER"
                ]
            }
        ]
    },
    ...
}'

200 OK
...

Make sure that the corresponding tags exist in order to apply the preferredPickingMethods in the above configuration.

In this example every incoming order or pickjob, which is tagged with the tag Consumer Groupis subject to this configuration. When such an entity is tagged with value B2C the created pickjob will contain the picking method BATCH while the tag value B2B results in picking method SINGLE_ORDER.

Creating a pickjob with given picking method via API

The following call would create a pickjob according to a given pickjob specific configuration:

curl --location --request POST 'https://your.api.fulfillmenttools.com/api/pickjobs' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '{
    "facilityRef": "0a3fe1dd-70d8-43b3-a70a-2cff78a4d439",
    "preferredPickingMethods": ["BATCH"],
    ...
}
'

201 Created
{
    "facilityRef": "0a3fe1dd-70d8-43b3-a70a-2cff78a4d439",
    "id":"96bd7ed8-cbfa-4c05-b8ae-6ab0ef647a74",
    "preferredPickingMethods": ["BATCH"]
    ...
}

Pick Job specific configuration: The field preferredPickingMethods within a Pickjob () tells you in which ways the pickjob expects to be processed. This configuration supersedes all other configuration around picking methods.

Facility specific configuration which says which picking methods are supported in which facility ()

Tenant wide configuration () of the default picking method: When a pickjob is created and no specific other configuration is provided (for example in the pickjob itself or the target facility) this default picking method is applied to a new pickjob

The defaultPickingMethod of the tenant can currently be set to one of the following values: SINGLE_ORDER, MULTI_ORDER or BATCH (see for details).

This configuration is considered a fallback configuration: It will only be used for new pickjobs if there is no facility configuration (see ) regarding picking methods in the target facility and no pickjob specific configuration (see ) regarding picking methods (upon creation via API for example).

The configuration of available picking methods within a facility is done in the itself. The parameter pickingMethods is an array that can contain none, some or all of the following values: SINGLE_ORDER, MULTI_ORDER or BATCH. The configured values tells about which kind of picking methods are performed in the corresponding facility and can be changed issuing a call like this:

This configuration overwrites a potentially present tenant wide configuration to picking methods (see ). A pickjob may override this configuration if it carries a different configuration regarding picking methods.

Link
Link
Link
Configurations of Picking Methods
facility
Configuration of picking methods in a facility
Configuration of the preferred picking method in a pickjob
Setting tenant wide default picking method
https://docs.fulfillmenttools.com/documentation
Example of how a batch pick run combines the articles of a single order