fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
    • 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
  • Description
  • Special configuration with tags
  • Examples
  • Example 1: A shipping label should be printed in the picking process
  • Example 2: A delivery note should be printed in the packing process
Edit on GitHub
  1. Order fulfillment
  2. Configurations

Printing & document configuration

PreviousHandover configurationNextParcel tag configuration

Last updated 5 months ago

Introduction

It is possible to add documents that are relevant in the operational process, for example, while picking or packing.

Available document types are:

  • Shipping label

  • Return label

  • Delivery note

  • Return note

  • External documents

It is possible to add different documents to different orders, pick jobs, pack jobs, etc. For adding external documents to the order process, please visit .

Please go to the for more information on handling printing and document configurations via API.

Description

A delivery and return note contain items of the corresponding picking task and carry additional information about the picked amount of each item. Both documents can be created on demand in the app.

External documents are documents which are not created within the fulfillmenttools system, such as invoices or individual coupons which are created in external systems. Those documents can be easily integrated into the printing process, so that a worker is able to print external documents within the fulfillment process with the app.

If a user decides to pick the task first she has the option to directly order a label for this task at the end of picking. While requesting a label, a -label is requested as well which is then attached to the normal label.

In order to create shipping or return labels, a is required. When is activated, printing within the picking process is not possible.

Special configuration with tags

It is up to the user, if the same documents should be used for each pick job / pack job or if the configuration should be more more detailed using via tags. Tags can be helpful to handle pick jobs and pack jobs differently. For example, marketplace orders may need other documents than orders from the company's own store.

Examples

Example 1: A shipping label should be printed in the picking process

Configure the “SENDLABEL” in the pick job. The picker can now start the pick job, click on the print button, print the label and do the following process steps.

Example 2: A delivery note should be printed in the packing process

Configure the “DELIVERYNOTE” in the pack job. Then it is only shown when clicking the print button in the pack job / packing process.

More information on tags can be found in the .

external documents page
return
carrier connection
batch picking
Developer Docs
Developer Docs