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
  • Concept
  • Implementation in fulfillmenttools
  • 1. Create an order including an interfacility transfer
  • 2. Picking and handover in supplying facility
  • 3. Picking in receiving facility
  • 4. Transfer process and goods receipt
  • 5. Finalizing the order
Edit on GitHub
  1. Order fulfillment

Interfacility transfer

Last updated 19 days ago

Introduction

An interfacility transfer describes the case where items should be transferred from one warehouse or store to another warehouse or store of the same retailer. In the fulfillmenttools platform it specifically describes moving items between facilities when a click & collect order is split during routing due to missing items in the receiving facility.

Concept

The interfacility transfer process involves two types of facilities: receiving and supplying. The process covers the following steps:

  1. Receiving Facility: The receiving facility's pick job lists expected items. Available items can be picked immediately, but picking may pause until all items arrive.

  2. Supplying Facility: The supplying facility sends missing items to the receiving facility, working like a "ship from store" process. Once handed over, a purchase order is created that includes a transfer ID (which helps identify the parcel).

  3. Item Transfer & Receipt: When the shipment arrives in the receiving facility, scanning the parcel triggers the receipt, which updates the pick job in the receiving facility with the newly arrived items.

  4. Final Picking: Once all items are available, the pick job is completed, and the order is ready for the customer.

Implementation in fulfillmenttools

Below, a step-by-step guide on implementing an interfacility transfer can be found.

1. Create an order including an interfacility transfer

Create a click & collect order and define the supplying facility in the order's delivery preferences under COLLECT/supplyingFacilitiesConfigurations:

  1. facilityRef: id of the facility that should supply the missing items

  2. deliveryEvents.deliveryTarget: set to "SHIP_TO_STORE"

  3. deliveryEvents.deliveryTrigger: set to "DEFAULT"

If no items are available in the preferred facility, the system will still route the order to the next best facility for fulfillment based on configuration settings. A pickJob will be created in the preferred facility with only expected items.

Example body information for a click and collect case
    "deliveryPreferences": {
        "collect": [
            {
                "facilityRef": "021e3402-ff49-4ec5-a907-af3b1e031c60",
                "supplyingFacilitiesConfigurations": [
                    {
                        "facilityRef": "e19ae843-0987-48bf-a182-a59997f937b0",
                        "deliveryEvents": [
                            {
                                "deliveryTarget": "SHIP_TO_STORE",
                                "deliveryTrigger": "DEFAULT"
                            }
                        ]
                    }
                ]
            }
        ]
    }

2. Picking and handover in supplying facility

  • The tasks can be monitored in the task view in the Backoffice (tasks are not marked as belonging to an inter-facility transfer).

3. Picking in receiving facility

  • A pickJob is automatically created in the receiving facility containing all items that should be picked in the facility as well as expected items that are still needed to be transferred from the supplying facility.

  • Users can start picking the already available items immediately.

    • The status of the pickJob is immediately set to open, allowing picking to begin for available items. Once all available items are picked, the status of the pickJob is automatically changed to WAITING_FOR_INPUT.

    • In a case only part of the expected items arrive in a delivery, picking can continue until all expected items have arrived. Only when all items are picked, the pickJob is finalized and marked as finished.

  • The pickJob can be monitored in the task view in the Backoffice. In the task overview, information on the facility from which items are shipped is display for expected line items.

4. Transfer process and goods receipt

  • After the handoverJob in the supplying facility is completed, an inboundProcess with a purchaseOrder is created automatically in the receiving facility.

If there are two or more handoverJobs from different facilities, an inboundProcess is created for each facility.

  • When the delivery has arrived in the receiving facility, it can be identified by scanning the transferId.

  • After the receipt is set to status FINISHED, the expected stock is added to the inventory of the receiving facility and the pickJob is updated, converting expected items into existing items.

5. Finalizing the order

  • After the missing items have arrived, the system updates the pickJob and:

    • Converts the expected items into regular items.

    • Changes the status of the pickJob to OPEN, allowing the picking process to continue or begin.

  • With all items picked, the entire order can now be packed and is then, ready for the handover to the customer.

The order can be monitored in the in the Backoffice

A regular pickJob is automatically created in the supplying facility containing all items that should be sent to the receiving facility. The pickJob can be carried out like any other "normal" pickJob via our .

Once the pickJob is processed and the items are packed, the handoverJob is completed and the items are handed over to a carrier who will ship the items to the facility specified in the order under supplyingFacilities. The hand over can be carried out like any other "normal" handOverJob via our . The address of the receiving facility will be displayed on the shipping label.

As soon as the purchaseOrder was created, the included items are announced in the receiving facility as expected stock. The transfer can be monitored in the in the Backoffice where it is marked as "internal".

The goods receipt can be performed via our . Alternatively, a receipt can be directly added to the respective inboundProcess via API.

Picking, packing and handover can be performed as usual via the .

Drawing
order view
Operations App
Operations App
inbound view
inventory app
Operations App