fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
      • Facility discounts
    • User management
    • GDPR
    • External actions
    • Notification center
    • Incident management
    • Tags
    • Stickers
    • Articles
  • Inventory Management
    • Overview inventory modules
    • Listing
    • Article categories
    • Stock
      • Stock availability
      • Stock properties
      • Stock updates
    • Reservations
    • Inbound process
    • Storage location
    • Zone
    • Inventory traits
    • Channel inventory
    • Measurement units
    • Stow jobs
    • External stock change reasons
    • Configurations
  • Availability & Promising
    • Availability & promising in customer journey
      • Earliest possible delivery date
      • Availability in delivery time period
      • Availability for specific delivery date
      • Checkout options
      • Delivery promise
    • Latest picking start
  • Distributed Order Management
    • Order management
    • Order routing
      • Fences
      • Ratings
      • Order split
      • Routing strategy
      • Item bundles
      • Re-route
      • Decision logs
      • Unroutable orders
      • Pre- and backorders
      • DOMS toolkit
  • Order fulfillment
    • Picking
    • Packing
    • Handover
    • Custom services
    • External documents
    • Load units
    • Interfacility transfer
    • Pick job target time
    • Configurations
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing & document configuration
      • Parcel tag configuration
  • Carrier management
    • Carriers and connection to facilities
    • Carrier country service mapping
    • Same day delivery
    • Custom carrier
    • Available carriers
  • Returns Management
    • Introduction to returns
    • Return reasons
  • Use Cases
    • Creating & executing stow jobs
    • Creating orders with interfacility transfers
    • Demand-driven replenishment
    • Expected stock in availability
    • Incoming goods & storage
    • Multi order picking
Powered by GitBook
On this page
  • Introduction
  • Scanning Type
  • Packing Container Required
  • Packing Item Confirmation Needed
  • Packing Source Container Configuration
Edit on GitHub
  1. Order fulfillment
  2. Configurations

Packing configuration

Last updated 5 months ago

Introduction

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 for more information on the packing configuration. A 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 ore 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.

packing REST API documentation
Developer Docs