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
  • Overview of Scanning Configurations
  • Additional information:

Was this helpful?

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

Scanning configuration

PreviousWeighed or measured productsNextPicking Methods

Last updated 5 months ago

Was this helpful?

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

Introduction

Users can define whether scanning of items and/or locations is mandatory during picking. In addition, the order in which both must be scanned can be defined. The scanning rules can be defined for each line item within the order / picking task, for each listing separately or in general for the whole tenant.

It is also possible to skip scanning rules completely with certain roles (Administrator, Supervisor).

For more technical information, see also

Overview of Scanning Configurations

There following configurations are currently available:

Configuration

Values

Impact

PickingScanCodeValidationConfiguration

CODE_MUST_BE_KNOWN

Default if not defined otherwise

When scanning, it is checked if the scanned barcode matches the defined scannable codes.

If it matches:

  • A snackbar (scan was successful) is shown

  • Picked amount is increased

If is does not match:

  • A snackbar (scan not successful) is shown

  • Picked amount is not increased

PickingScanCodeValidationConfiguration

NO_VALIDATION

When scanning, it is not checked if the scanned barcode matches the defined scannable codes.

Every scan (in the picking detail view) of any barcode results in:

  • Increasing the picked amount by 1

  • No snackbar (scan successful or not) is shown

PickingScanningConfiguration

MUST_SCAN_FIRST

Before being able to manually increase the picked amount in the client, a scan of the item must be performed.

Otherwise it is not possible to use the + and - buttons to change the picked amount of the item.

PickingScanningConfiguration

SCAN_NOT_REQUIRED

Default if not defined otherwise

It is possible to use the + and - buttons to change the picked amount of the item without scanning the item beforehand.

PickingScanningConfiguration

Each item must be scanned individually and cannot be picked manually.

scanningRule

ARTICLE ONLY

{"scanningRuleType": "ARTICLE", "priority": 0}

LOCATION ONLY

{"scanningRuleType": "LOCATION", "priority": 0}

ARTICLE THEN LOCATION

{"scanningRuleType": "ARTICLE", "priority": 0}{"scanningRuleType": "LOCATION", "priority": 1}

Configure which scannable codes should be scanned in which priority

  • Set via picking config: tenant wide configurations when

  • Set via facility: overrules picking config and rule applies only for this specific facility

  • Set via listing: overrules picking and facility config and applies only for this specific listing. Configure which scannable codes should be scanned in which priority (lowest must be scanned first)

    If the "LOCATION ONLY" option is selected, the storage locations must be type "Single Storage Location" and should exclusively contain one type of product. Otherwise, scanning the location for picking purposes may not yield successful results.

rolesWithOverwritingScanningPermission

"ADMINISTRATOR", "SUPERVISOR"

When this configuration is set, the scanning rules are skipped entirely for those user roles. This means that a Supervisor or Administrator is able to pick items without scanning at all by using the manual input option while picking.

Additional information:

  • If the scanningRule is not specified, the default rule is set to "ARTICLE ONLY."

  • If both MUST_SCAN_EACH and "ARTICLE" are selected, and the scanning option "LOCATION" is chosen, the location must be scanned only once, while the article can be scanned multiple times for the specified item as needed.

  • If either MUST_SCAN_FIRST or MUST_SCAN_EACH is active, and the scanning option is set to "LOCATION ONLY," each scan of the location contributes to the cumulative total of the chosen amount.

MUST_SCAN_EACH
https://docs.fulfillmenttools.com/documentation
Scanning Configuration